EngineeringDelivery
Tickets closed in the last 30 days: how long they took, where the time went, and who worked them.
Headline figures
Elapsed calendar days from each ticket's Jira status history, not logged effort: nobody logs time in this project. Tickets closed without ever being in dev, QA or blocked are backlog clean-up; they are counted but left out of every time figure.
Forecast · when the current queue clears
A projection, not a commitment. It replays the last 12 weeks of delivered tickets at random until the queue is empty: half the simulated outcomes finish by the likely date, 85% by the cautious one. It assumes no new work arrives, that the tickets ahead resemble the ones behind, and it knows nothing of leave or work outside Jira.
Forecast by stream
Each stream's queue against its own delivery rate.
When each engineer is free
What each person holds in dev or blocked, and Dev Ready tickets assigned to them, against the tickets they delivered. Anyone with fewer than 10 delivered in the history gets no date: there is too little to go on.
Days per stage
Per delivered ticket. A long-idle ticket closed this month pulls the average up, so read the median first. Waiting is everything before dev and between stages.
Closed per week
Week starting Monday. The darker bar is delivered work, the lighter one clean-up.
Delivery by stream
Delivered tickets only. Cycle is the median, in days.
By engineer
A ticket counts for whoever held it longest while it was in dev (or in QA, for the QA columns). Tickets differ in size and are not estimated, and a status changed late shows as minutes in dev, so treat these as questions to ask, not scores.
Closed tickets
Days in each stage. Click a column to sort.