Anyone. Anyone who can see the board. Updated 8 November 2026

Sprint History: read every chart

One short section per chart, with what it shows, what to look for and how it is counted. Anyone can read it, in about 8 minutes.

8 minutes · anyone who can see the board

Steps

  1. Overview: the plan shelf

    The main chart. Each jar is one sprint, oldest on the left. The outline is what was planned at the start, and an empty part means it wasn’t finished. The fill is what finished from that plan.

  2. Joined later and taken out

    The dotted block on top is work that joined later and finished. It sits on top so it never makes the plan look bigger. Hatched is work that was taken out before the sprint closed. A dashed outline is the sprint that is still open, with “day 6 of 10”.

  3. The usual band

    The grey band is “usual”: the range of finished-from-the-plan, leaving out the highest and the lowest. A sprint that doesn’t count says “left out” and why: no sizes, nothing finished, very short, ran in parallel, or another board. “Key” shows the legend.

  4. The headline

    The headline says it in percent: “This team usually finishes 95 to 100% of what it planned, plus about 3 points that join later.” Under the jars: “Last 10 sprints, leaving out the highest and lowest”. Some teams call the percent the say/do ratio.

  5. How it differs from Jira’s chart

    Jira’s velocity chart shows committed and completed. This chart separates what finished from the plan from what joined later, and counts every item once, at the size it had when it entered the sprint.

  6. Count by and Split by

    Where they show, “Count by” switches between “Points”, “Items” and “Hours”, and “Split by” colors the jars by “Type”, “Epic”, “Label” or “Component”. Groups with under 5 items are drawn hollow because they are too few to read.

  7. Sprints: open one sprint

    Click a jar, or open the “Sprints” tab. The sprint sheet shows “What happened to the plan”: “Planned at the start”, “Finished from the plan”, “Joined later”, “Taken out”, “Won’t do”, “Resized” and “Not finished”, each with its work items. In Sprint 40, for example, 32 points were planned and all 32 finished, and 8 more joined later and finished.

  8. Who, and what next

    Open “By person” to see who had each finished item when it finished, and “Open the item in Jira” opens it. “Copy a line for the retro” gives one sentence for your retro. Arrows step to the earlier or later sprint, and “Earlier sprints ›” reads sprints older than the last twelve.

  1. Worth a look

    A card on the Overview lists what stands out, like “2 items have no estimate”, sprints that finished nothing, a jar left out, or work items running long for their size. “Nothing stands out. This team’s history reads cleanly” is a good answer.

  2. The line that compares with Jira

    One line compares with Jira: “Jira likely shows 36 for Sprint 46; this count is 34.” “Why” shows every step from Jira’s number to this one.

  3. Sizes

    The “Sizes” tab, and the “Our sizes” card on the Overview. Rows run 1s, 2s, 3s, 5s, 8s and 13s, for example “5s: 15 of the last 15 took 3 to 6 days” and “8s: 8 of the last 9 took 5 to 8 days.” That is start to done in working days.

  4. How steady a size is

    A small bar shows each size’s usual range and a word for how steady it is: “steady”, “fairly steady”, “varies a lot” or “hard to predict”. “Early read” means only a few have finished.

  1. Open a size

    Click a size for its sheet: the items, longest first, and “Two sizes side by side”. The bottom lines say whether a bigger size really takes longer: “When an item was sized one step bigger, it took longer 80% of the time (91 items compared).”

  2. Copy it

    “Copy as our size guide” puts the table on your clipboard. “Split by” splits sizes by type, epic, label or component.

  3. Flow: sprint progress

    The “Flow” tab has five pages. “Sprint progress” is a burn-up for one sprint, day by day: for example “26 of 40 points done, 6 in progress”. The sprint’s scope is a line that steps up when work joins (“+3 Wed”) and down when work is taken out.

  4. The usual pace

    A band shows the usual pace for the same day from past sprints. The headline says where you stand: “Sprint 47 is at its usual pace.” Use the left and right arrow keys to move between days; each day lists what finished, joined or left. “Split by” colors the done part.

  1. Flow: finished per week

    “Finished per week” shows items finished each week as bars (or dots), with the usual week as a band: “This week: 0 points finished so far. A usual week here is 0 to 24 points.” On Kanban boards it is the headline.

  1. Flow: how long

    “How long” is cycle time. Each dot is a finished item, placed by the day it finished and how long it took, in working days, Monday to Friday. Choose a window: “30 days”, “90 days”, “6 months” or “2 years”. “Dots” and “Bars” change the view.

  2. The number to quote

    “85 of every 100 items took 6 working days or less. Half took 3 or less.” That 85-of-100 line is the number to quote when someone asks how long it takes. With too few finished items you get “Too few finished items to say what is usual yet.”

  1. Where the time went

    “Where the time went” shows how long items sat in each status.

  2. Split by type or size

    “Split by” offers “None”, “Type” or “Size”. Type gives one row per work type on the same time axis, so you can see whether bugs take longer than stories: “62 items · half within 3 days · 85 of 100 within 5.5”. Click a name to focus on one. A row with too few items says “too few to say”.

  3. Flow: needs a look

    “Needs a look” is ageing work in progress. It lists items in progress, with each one’s age in working days. This is the page for stand-ups: “Your 1 item in progress has been there longer than usual for its column.”

  4. Why an item is flagged

    An item is flagged when it is older than most items were when they left that column, or longer than its size usually takes. For example, an item 6 days in reads “Longer than a 3 usually takes here (up to 4 days). Most items had left In progress by day 4.” Enter opens an item in Jira.

  1. Flow: piling up

    “Piling up” is a cumulative flow diagram. It shows items in each working column week by week, from the first column to the last. Read the widths of the bands, not the height of the top. “Split by” breaks one column down.

  2. Where work waits

    A column that keeps growing is where work waits: “In review is filling: is Done keeping up?” When work flows evenly, the headline says so instead: “Work is flowing evenly: about 9 items start and 9 finish each week.”

  1. People

    The “People” tab shows each person’s finished work against their own usual range: one small bar per sprint with the points under it, the usual range as a band behind the bars, and, for example, “Usually 0 to 26” at the end of the row.

  2. Quiet people and credit

    Someone who was quiet for a few sprints is left out of the averages (“Left out of the averages: quiet for 2 sprints”), and “Include” adds them back. Credit goes to whoever had the item when it was finished. The usual is each person’s own, never a comparison between people. A Jira admin can switch people views off for the whole site.

  1. Numbers behind each chart

    Charts have a “Numbers” link. It opens “Numbers behind this chart”: the table the chart is drawn from, “Per sprint” (planned, finished from plan, moved on, taken out, joined later, % of plan) or “Per item” with days in each board column.

  2. Copy or download

    “Copy table” copies for a spreadsheet, and “Download CSV” saves a file that opens cleanly in Excel. The “Copy summary” menu has the same: “Numbers behind this chart ›” and “Every item, days in each status (CSV)”. In the Free app the per-item days are in the full app.

If something’s off

  • A jar has no number.

    It is still open, or it is left out. The jar says which.

  • A page says “Reading this sprint” or “Reading the weeks”.

    The first read is still running. It fills in.

  • “Split by” shows nothing to split by.

    You see “Nothing to split by here”. The work in those sprints has no type, epic, label or component to split on.

  • “Earlier sprints” is greyed.

    Sprints older than the first 12 are in the full app.

Still stuck?

Write to support@unitlane.net. Tell us what you clicked and the exact words you see.

Go to the support page