Sprintwell documentation
Sprintwell adds six gadgets to Jira Cloud dashboards: velocity chart, sprint report, sprint burnup, sprint burndown, scope change and sprint health. Each one reads a scrum board's sprints and rebuilds them with the same rules as Jira's own sprint report and velocity chart, and every number can be opened to the work items behind it. It runs entirely on Atlassian's Forge platform.
Get started
- Open a dashboard (Dashboards > View all dashboards) and choose Edit.
- Choose Add gadget (classic dashboards) or Add widget (the new dashboards), search for Sprintwell and add Velocity chart (Sprintwell).
- In the gadget's settings, find your team's scrum board and pick it. On classic dashboards click Save; on the new dashboards save the dashboard.
- Click any sprint's bars to list the work items behind them.
Add the other gadgets the same way. A Jira admin can set the site's working days, holidays and time zone in Jira settings > Apps > Sprintwell.
How Sprintwell counts
Sprintwell follows Jira's sprint report:
- Committed: work items in the sprint when it started, with their estimate at that moment.
- Added: work items that joined after the start (including items created straight into the sprint), with their estimate when they joined.
- Removed: work items that left before the sprint was completed, with their estimate when they left.
- Completed: work items in the board's right-most column when the sprint was completed (or now, for the running sprint), with their estimate at that moment.
- Completed outside the sprint: work items that were already done when they joined (or when the sprint started) and stayed done. Jira leaves them out of velocity, and so does Sprintwell.
- Not completed: still in the sprint at the end and not in the right-most column.
- Re-estimated: estimate changes made while a work item was in the sprint.
The totals always add up: committed + added - removed + re-estimates = scope at the end = completed + completed outside + not completed. Sub-tasks are counted with their parents, as in Jira. Work that Jira moves to the next sprint when a sprint closes still counts as not completed in the sprint it was in.
Measure
By default a gadget measures with the board's estimation field (Board settings > Estimation), which is what Jira's own reports use. You can measure with any other number field, or count work items instead. Time fields show in hours.
The gadgets
Velocity chart
Committed (grey) against completed (blue) for the last 3 to 20 closed sprints, plus the running sprint in a lighter bar. The orange line is the rolling average of completed work (2 to 6 sprints). Under each sprint: say/do, completed divided by committed. Above the chart:
- Average and Last N: completed work per sprint.
- Say/do: average of each sprint's completed divided by committed.
- Committed work finished: of the work committed at the start, the share that was completed (measured with the estimates at the start), across the sprints shown.
Add up to five more boards in the settings to compare teams on one gadget.
Sprint report
For one sprint (the last closed one by default, or the running one, or any sprint you pick):
tiles for committed, completed, added, removed, not completed and say/do, a bar of the outcome,
and the lists of work items, each with its status, its estimate at the start and at the end
(5 → 8 when it changed) and when it joined.
Sprint burnup and burndown
Scope (grey) and completed work (green) through the sprint, or the remaining work (blue) against the guideline from the commitment to zero at the sprint's end date. Orange dots mark work added, red dots work removed, gold dots re-estimates; hover for the work item. Changes lists every change with the totals after it. Hide non-working days removes weekends and holidays from the time axis; untick it to see them shaded.
Scope change
One column per sprint: work added (orange) and re-estimated up (gold) above the line, removed (red) and re-estimated down below. On top: churn, everything that moved as a share of the commitment; underneath: the net change. Click a column for the list of changes.
Sprint health
For the running sprint: a verdict (on track, at risk or behind), time elapsed against work done, the status split (to do, in progress, done), scope change since the start, remaining work and working days left, flagged and unestimated work items.
- Behind: more than 25 points of percentage between time elapsed and work done.
- At risk: more than 10 points, or scope grew more than 20%.
Working days
Burnups, burndowns and sprint health use working days. The site defaults (Jira settings > Apps >
Sprintwell, Jira admins) apply to every gadget; a gadget can untick Use the site defaults and
set its own working days, holidays (one YYYY-MM-DD per line) and time zone.
Exports
- CSV: velocity (one row per sprint), sprint report and sprint health (one row per work item with outcome and estimates), burnup and burndown (one row per change), scope change (one row per sprint). Opens in Excel and Google Sheets.
- PNG: the chart with its title, at twice screen resolution.
Some browsers block downloads from embedded frames; the CSV is then copied to your clipboard and the gadget says so.
Permissions and privacy
Every gadget reads Jira as the person looking at it, so two people can see different numbers if they can browse different work items. Sprintwell never changes anything in Jira. Computed sprints are kept per person for a short time (closed sprints 7 days, the running sprint 3 minutes) so gadgets open quickly; Refresh reads the sprints again.
Limits
- Scrum boards only.
- 2,000 work items per read of a board's sprints.
- Work items removed from a sprint are found among the board's work items that changed since the sprint started; when more than 5,000 changed, the gadget says the list may be short.
- Work items moved to a project outside the board's filter after being removed are not found.
- The first read of many sprints takes a few seconds; the gadget shows its progress.
Support
hello@greatwork.company, or the help desk link on the Marketplace listing. We answer within one business day.