Scope Creep & Churn for Jira

For one sprint, the gadget shows what was committed when the sprint started, what was added and removed afterwards, who did it and on which day, and how much of the original commitment was delivered.

Set up

Add the gadget, open its three-dot menu, choose Configure and pick a board in Scrum board. The settings list the first 200 boards; type part of a name to search them all. The gadget then offers that board's active sprint and its 15 most recently closed sprints; use the list in the gadget to switch between them. It works with company-managed and team-managed Scrum boards. Classic Kanban boards have no sprints and are not offered; a team-managed board without sprints shows a message instead.

What the numbers mean

FigureDefinition
Committed at startWork that was in the sprint when it started, in story points (or issue count when the sprint has no points)
AddedWork that joined after the start. "In the second half" counts additions after the middle of the planned sprint
RemovedWork that left the sprint after the start and is not in it at the end
Scope creepAdded divided by committed
Churn(Added + removed) divided by committed
Commitment deliveredCommitted issues that were in a Done status category at the end of the sprint, each counted at its start estimate, divided by committed. An issue re-estimated upward during the sprint still counts at its start estimate, so the share cannot pass 100%. For an active sprint, "the end" is now
FinalWork in the sprint at the end, at end estimates

An issue that was removed and later put back counts as unchanged. An issue that was added and then removed again is listed in its own table, "Added, then removed again", and does not count as added. When an issue joined before it had an estimate, it is weighed by the first estimate it got inside the sprint.

"Re-estimated while in the sprint" lists issues whose story points changed after the start, with the old value, the new value and the date. The note under the daily chart gives the net effect of those changes on scope.

The daily chart shows scope and completed work at the end of each UTC day.

How it works

The gadget rebuilds the sprint from Jira's change history: the Sprint field for who was in the sprint, the estimation field of the board for points, and the status history for what was done at a given time. "Done" means the Done status category, not the resolution field, so workflows without resolutions work.

Issues that left the sprint are no longer returned by a sprint query. The gadget finds them by searching the board's filter for issues that changed since the sprint started and are not members now.

Limits