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

Sprint Forecast: read every part of the answer

Every part of the Sprint Forecast screen, what it shows and how it is worked out. Anyone can read it, in about 6 minutes.

6 minutes · anyone who can see the board

Steps

  1. The answer

    One sentence on a colored band: “Likely fits, with 1 to 2 days to spare”, “Too close to call”, “Likely needs about 3 more days”, “Fast enough, but unlikely to finish every item” or “Not enough finished work yet.” “Likely” means at least your aim in 10. The band color follows the answer, and the words always say it too.

  2. The proof under it

    For example: “4 of your last 10 sprints went fast enough to finish all 20 points by Fri, Nov 13. The other 6 needed 1 to 3 more days.”

  3. Where the proof comes from

    The app took each of your last sprints, replayed its real pace day by day on this sprint’s work, and counted how many finished everything by the sprint’s end. That count is the odds. No made-up curve, just your own history.

  4. Your aim

    The chip “Aim for 8 in 10” is how sure you need to be. Choose it to open “Settings” and pick “Normal · 6 in 10”, “Careful · 7 in 10”, “It matters · 8 in 10” (the usual choice) or “A release depends on it · 9 in 10”. A higher aim asks for more days to spare. It is saved for the whole board.

  5. The picture: past sprints on the finish day

    Each little character (or dot, if you pick “Plain dots, no characters” in the ••• menu) is one past sprint, standing on the day it would have finished this plan at its own pace. Sprints that tie share a stack.

  6. In time or not

    Left of the “Sprint ends” line means in time. The ones on the right, labeled like “6 sprints need more days”, needed more, marked “+1”, “+2” and so on. The bracket at the top says, for example, “4 done by Fri, Nov 13”.

  7. Point and click

    Point at one to see which sprint it is, how fast it was (“fastest of the 10”), and what it means: “At its pace, this plan needs 3 more working days after the sprint ends.” Click it to see that sprint’s items. Public holidays show on the day line.

  8. Notes

    When something about your board could change the answer, a chip says “Note:” with a short sentence, like a status to the right of Done, or items with no estimate. Choose it to open “Notes”. Each note says what the app did about it, and shows both outcomes when it matters.

  9. What would make it fit

    When the plan is too big, a block says what to leave out: “Leave out KIWI-479 and KIWI-476 (8 points, last in your order) and it’s 8 in 10.” Then: “Or keep everything: likely needs about 1 more day.”

  10. Try it on your screen

    “KIWI-479 decides most” names the work item with the most influence. “Try it” applies the suggestion on your screen, “Put back” undoes it, and “Other ways” lists more choices. In the Free app this block is muted: “What would make it fit · in the full app”.

  11. The list and the cut line

    The row “Items in this sprint” opens the sprint’s work items in your board’s order, with each item’s size. The cut line separates “Very likely” (above) from “Stretch” (below). Drag it to try other odds, for example “8 points · 8 in 10”. Nothing you try is saved in Jira.

  12. Try other plans

    “Highlight” shows where an epic, a label or a work type sits against the line. “Try adding a work item” lets you pick a backlog item and see the effect, for example “With KIWI-501: 6 in 10”. “Show in backlog” opens the sprint in your backlog.

  13. Time

    For example “30 of the team’s usual 40 person-days”. Public holidays and marked away days come off, and people who have been quiet for two sprints are left out. Choose “Add time off” to mark a day. On an hours board the line speaks in hours of estimates.

  14. People

    For example “Everyone counted has their usual load” or “Cleo has more than usual: 6 points, usually 2 to 4 in 10 days.” “Heavy”, “Usual” and “Light” compare each person with their own usual range, never with each other.

  15. The Team tab

    The “Team” tab opens each person’s days, away marks and public holiday region. In the full app it also shows work on other boards, counted as time, and “Group by” component or label.

  1. Past forecasts

    The app keeps score of itself. A line under the facts says, for example, “Forecasts said about 8 of the last 10 sprints would finish everything. 9 did; Sprint 41 didn’t.” “Show” lists the calls as marks. Until there are enough, you see “Past forecasts show here after 5 sprints”.

  2. The Track record tab

    The “Track record” tab holds the full list, with the count line above it. A sprint that finished everything reads “Forecast 8 in 10 · all finished · recalculated afterwards”. One that didn’t says, for example, “2 items moved to the next sprint”.

  1. When the team changes

    If fewer sprints fit than the forecasts said, you see “Fewer sprints fit than the forecasts said. That often means the team changed” with “Count from” the sprint after the change.

  2. Chance each day

    The “Track record” tab also draws “Chance each day”: the chance on each working day of the sprint, against the range your past sprints reached on the same day.

  3. Why it moved

    Under the answer, a line says what changed since you last looked, like “Since you last looked (Tue): 2 items added (5 points). 7 in 10 → 5 in 10.” “Why” opens “Why it moved”: “Added work”, “Estimate changes”, “Finishing pace” and “Time”, each with its effect. “Undo” shows on a change you can reverse.

  4. The footer says “A forecast from your last 10 sprints, not a promise” and, on the right, “As of 11:06 AM”, when the answer was last worked out.

  5. The work item panel

    On a work item in an active or upcoming sprint, the “Sprint Forecast” panel says whether the item sits in the very likely part of the plan, in the stretch part, or is done. You add it from the work item’s app menu. “Open the forecast at this item” jumps to it.

If something’s off

  • The picture has fewer characters than you expected.

    Sprints with no work, no dates or under an hour are left out. Open “How it’s counted” to see which and why.

  • You see “Not enough sprints to call yet.”

    The forecast starts once 3 sprints have finished.

  • A sprint is overdue.

    You see “This sprint has passed its end date and is still open, so the days it needs are counted from today.”

  • The sprint you picked has closed.

    You see “Sprint 46 has closed.” A forecast looks ahead. Choose “Go to the sprint that is running”.

Still stuck?

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

Go to the support page