The Sprint movement report helps improve your team’s efficiency by tracking how much work your team is completing and adding during your sprints. Sprint movement provides a visual analysis of your team’s completion and scope added percentages over the course of one or more sprints.
Who can use this?
Use the Sprint movement report to track how well your team accomplishes goals they’ve set and help your team stay focused.
In this article
Sprint movement tracks up to six sprints from your ticket vendor to use for your report. Only completed sprints appear in Sprint movement. Sprints currently in progress do not appear in Sprint movement.
Use the filters to choose which team and sprints you want to see:
- Select your team using the team filter.
- Toggle whether to include or exclude nested teams from the report.
- Select between one and six sprints using the sprint search filter.
Reading scope analysis
Sprint movement’s scope analysis tool provides a detailed review of your team’s efficiency during your sprints.
Sprint movement uses completion and scope analysis percentages to show how your teams are working. These metrics are represented both visually and numerically.
Note: Sort the information in Sprint movement by either tickets or story points. To switch your view, use the toggle at the top right of the scope analysis section.
On the right side of the scope analysis section, see a visual representation of your team’s work over the selected sprints.
At the bottom, see a bar chart of the number of tickets or story points from each category, represented from left to right:
- The green bar on the left of each sprint represents the total number of tickets or story points completed.
- The blue bar in the center of each sprint represents the total number of tickets or story points completed that were committed to at the beginning of the sprint.
- The purple bar on the right of each sprint represents the total number of completed tickets or story points that were added to the sprint after it started.
- Each bar is compared to a grey bar. The grey bar represents the total number of tickets in that category.
Hover over a sprint to see more information.
Above these bar charts, see a scope percentage graph. The blue section, on the bottom of the graph, represents the percentage of work originally committed. The purple represents the percentage of work added after a sprint started.
The green line represents the total number of completed tickets. It shows you how you’re tracking against your commitment.
- Above commitment: If the green line is above the blue section, you completed more than the amount of work you planned for.
- Met commitment: If the green line is right on the line between the blue and purple sections, you completed exactly the amount of work you planned.
- Below commitment: If the green line is below the blue section, you were not able to complete the work you planned.
To see more information for a particular sprint, click on the sprint in the graph. On the right side of the scope analysis section, see a numerical breakdown of the completion percentage, scope added percentage, and ticket completion numbers for that sprint.
Tip: If you want to see more about what happened during that sprint, click View Retrospective to see that sprint in the Retrospective report.
Use this information to gauge how your team is performing against its commitments and whether you need to rebalance your work.
Flow calculates completion percentage by dividing the number of completed tickets or story points by the total number of tickets or story points in the sprint when it finished.
Note: Completion percentage includes both committed work and work that was added to the sprint after it started.
Use completion percentage to see how much of their work your team completed during the sprint. Keep an eye on the completion percentage to make sure your teams are setting challenging, but realistic goals.
Scope added percentage
Flow calculates the scope added percentage by dividing the total number of tickets or story points added after the sprint began by the total number of tickets or story points in the sprint.
Note: The total number of tickets or story points is calculated at the end of the sprint. It includes all added tickets or story points.
Use the scope added percentage to keep an eye on how often your teams have unplanned work in their sprints. Having some change in tickets after a sprint starts is normal. Too much change means your teams aren’t able to plan their work reliably. If that happens you should take a look at how you might help teams better plan for their sprints.
Viewing ticket details
Click on a sprint in the Scope analysis section to get a more detailed view of the work that went into a sprint.
This opens a list of tickets below the Scope analysis section. These tickets are from the sprint you selected.
This list of tickets shows the metrics related to the ticket, including the sprint outcome. If the circle in the sprint outcome column is filled in, that ticket was completed during the sprint. If the circle is open, the ticket was not completed during the sprint. Click on the ticked ID to view the ticket in your vendor.
Note: The Sprint Outcome column represents the status of the ticket when the sprint ended. It will not change. To see what the current status is, use the current status column.
To filter your tickets more, use the Scope type and Scope completion filters.
The Scope type filter lets you choose whether you view tickets you committed to at the beginning of the sprint, tickets that were added after the sprint started, or both. The Scope completion filter lets you see tickets that were completed, tickets that remained uncompleted at the end of the sprint, or both.
If you need help, please email Support (opens email form) for 24/7 assistance.