While you deliver
Lead Time and Aging Analyzer
See how long your team's work really takes, as numbers you can plan with, and find the open items that have already taken longer than almost everything you finish.
Read an export from Jira, Azure DevOps, Asana, Trello or a spreadsheet, as .csv or .xlsx, inside your browser. Nothing is uploaded.
Tracker export
Drop a spreadsheet here
From Jira, Azure DevOps, Asana, Trello or a spreadsheet: one row per item, with a status, a created date and a done date.
Percentiles, not averages
Lead times are lopsided. Most items finish quickly and a few take ten times as long, so the average describes no item anyone recognizes. The tool reports the 50th, 85th and 95th percentiles instead: half the items finished within this many days, 85 percent within that many. When someone asks how long a piece of work will take, the 85th percentile is a fair answer, and it comes from what the team has actually done.
Lead time and cycle time
Lead time runs from the day an item was created to the day it was done. Cycle time runs from the day work started, when the export records it; Azure DevOps exports an activated date, and Jira can with a custom field. With only created and done dates, which every export has, lead time still works, and it reads support tickets as well as backlog items.
Aging work
An item in progress for 40 days on a team that finishes 85 percent of its work within 18 is almost certainly stuck, but on a board sorted by priority it looks like everything else. The tool sets every open item against the finished ones and ranks them by how unusual their age has become, so the conversation starts with the items that need it.
Any tracker
It finds the key, status, created and done columns under their usual names in each tool’s export, reads dates in any of their formats, and sorts every status into not started, in progress, done or dropped. Items resolved as Won’t Do or Duplicate are left out. Every reading is shown and can be changed.
What this does not do
It measures the past; the Delivery Date Forecast turns the same history into a range of dates. Without a start date, an item that sat in the backlog before anyone picked it up looks older than it has been in progress. And a percentile from a handful of items says very little, which the page will say when it happens.