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

Scrum, Kanban and team-managed boards

See what each app shows on Scrum, Kanban and team-managed boards, and what is different. Anyone can read it, in about 3 minutes.

3 minutes · anyone

Steps

  1. Scrum boards

    The full experience. Sprint Forecast answers “Will this sprint fit?” for the active or next sprint. Sprint History shows jars for the last sprints, the sizes behind them, and the flow pages.

  2. Kanban boards

    A Kanban board has no sprints, so there is no sprint to fit. Sprint Forecast says “This board doesn’t use sprints” and the first tab is called “Now”. It moves straight to what Kanban boards do have: likely dates for epics and releases, worked out from the last 20 weeks of finished work.

  3. The Now tab

    The dates sit on the right. A board with no epics or releases yet shows “Dates come from epics and releases” and a “When will it be done?” button there instead. Once there are dates, the footer says where they come from: “A forecast from your last 20 weeks of finished work, not a promise.”

  4. Waiting now

    “Waiting now” lists work that has been in progress longer than 85 in 100 finished items took. There is no “Track record”, because there are no past sprints to grade.

  5. Sprint History on Kanban

    Sprint History tells history week by week: the headline is “Finished per week”, and every item counts once in the week it finished. The flow pages work as on a Scrum board: “How long”, “Needs a look” and “Piling up”. Kanban boards count in items.

  1. Team-managed boards

    Team-managed (formerly next-gen) projects work the same way. The board’s columns are its statuses, so choosing the finished columns works with the same tiles. Sizes come from the estimate field of the project, if it uses one. Without one, the apps count items.

  2. Boards that share sprints

    When two boards share a sprint, each app counts only the items that belong to the board you are looking at. A note says “This board shares its sprints with another board, so some work may count on both.” If two sprints ran at the same time on one board, the note says so, and those sprints are left out of the usual range.

  3. Sprints that don’t count

    A sprint that has no dates, is shorter than an hour, or has no work is left out of every count. The jar and the sprint line say why.

  4. A board with little history

    Both apps wait to say what is usual until three sprints have finished. Until then they show what exists and call it rough.

  5. Borrow another board’s history

    Sprint Forecast can use another board’s finished sprints for the pace until the new board has enough of its own. The offer says “Use history from Kiwi board” and needs 5 finished sprints that you can see. Then the screen says “Using Kiwi board’s last 10 sprints.” It switches back by itself, with a line to tell you.

  6. Which kind of board is it?

    Not sure what kind of board you have? Open the Get started page of the app: each board in the list is labeled “Scrum board”, “Kanban board, no sprints” or “Team-managed board”.

If something’s off

  • A Kanban board shows no “Will this sprint fit?”.

    Correct. Use the dates for epics and releases.

  • A team-managed board shows items instead of points.

    Its project has no estimate field in use. Turn one on in the project’s settings in Jira, or use items.

  • Work is counted on two boards.

    That is the shared-sprint note. Each board counts its own items.

Still stuck?

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

Go to the support page