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.
Steps
-
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.
-
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.”
-
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.
-
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.
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.