Sprint Metrics Overview
Sprint metrics can help you plan and deliver on sprints more effectively, including backlog grooming and story hygiene. These metrics can help you address business problems like:
Do teams consistently deliver on sprint plans? If not, why?
What is the impact of creep or un-estimated tickets on plans?
Are teams overburdened or underutilized by the sprint plans?
Onboarding Path
These examples show how you can use sprint metrics to measure team performance.
Use sprint metrics reports to analyze sprint and planning metrics.
List of all the metrics supported in SEI for measuring sprint success.
These ratios are calculated from sprint metrics.
Step by step guide to create a Sprint Insight
Recommendations to improve your Sprint Metrics reporting
Sprint metrics use cases
These examples show how you can use sprint metrics to measure team performance.
Measure team performance in recent sprints
Use the commit done ratio to check the team's performance on recent sprint plans. Compute this metric as an average over the last 2 months or 6 sprints.
If the average commit done ratio over a long period of time is above 70 per cent, then the team is executing sprint plans well and could potentially take on more load. If the total done to commit ratio is above 120 per cent, then the sprint plans aren't making full use of the team's capacity.
A commit done ratio below 60 per cent indicates poor performance on sprint plans and room for improvement in sprint delivery. There are several reasons a team might perform poorly on sprint plans. Check for:
The impact of creep and context switching on sprint plans. Check the creep to commit ratio and the creep done to commit ratio. Creep that is consistently above 40 per cent could have an impact on sprint deliverables.
Vague requirements that cause rework and impact sprint delivery. Use an Issue Hygiene Report to check the sprint's Hygiene Score.
If none of the above apply, then the team may be consistently planning for more than they can deliver.
Here is a flow chart illustrating the use of sprint metrics for performance analysis:
Analyze sprint performance
This example analyzes team performance over a sprint, as represented by the following JIRA sprint report:
LO-1
2
Done
Completed in the sprint
LO-2
1 -> 2
Done
Points changed from 1 to 2 mid-sprint, completed in the sprint
LO-3
5
Done
Creep, completed in the sprint
LO-4
5
In Progress
Not completed
LO-5
1
In Progress
Creep, not completed
LO-6
1
Done
Completed outside the sprint
LO-7
1
To Do
Removed from sprint
The following table represents how the above JIRA sprint report is interpreted by SEI:
LO-1
Done
2
2
2
-
-
LO-2
Done
1
2
2
-
-
LO-3
Done
-
-
5
5
5
LO-4
In Progress
5
-
-
-
-
LO-5
In Progress
-
-
-
1
-
LO-6
Done
1
1
1
-
-
LO-7
To Do
1
-
-
-
-
Total
-
10
5
10
6
5
SEI uses the above points values to calculate sprint metrics ratios, generating the following sprint performance analysis:
Commit done ratio
5/10=50%
Indicates poor performance on the plan.
Done/Delivered to commit ratio
10/10=100%
Indicates an overall good job delivering on commitments.
Creep to commit ratio
6/10=60%
Indicates too much creep in the plan.
Creep done to commit ratio
5/10=50%
Poor performance on the plan is explained by creep.
Use historical metrics for sprint prediction and performance assessment
You can use historical cycle time data and key metrics to evaluate a team's performance, predict the number of items that can be completed in the next sprint, enhance sprint planning, and improve overall efficiency.
Use Sprint Metrics Single Stat widgets to present sprint metrics or sprint metrics ratios on your Insights, such as the done to commit ratio, scope creep (unplanned work) ratio, sprint velocity, or creep to commit ratio.
After configuring the widgets, use the provided statistics to estimate the number of items for the next sprint, evaluate performance, and identify trends.
Sprint metrics reports
Use sprint metrics reports to analyze sprint and planning metrics.
Sprint Goal Report
Sprint Distribution Retrospective Report
Sprint Impact of Unestimated Tickets Report
Sprint metrics
Sprint metrics measure points and tickets in a sprint. This includes work that was planned (committed), completed (done/delivered), incomplete (missed), or added after the sprint started (creep).
Sprint work is typically measured in story points, which are a relative estimation unit used to gauge the complexity and effort required for a task. Point can represent expected level of effort, complexity, or value of tickets.
The key sprint metrics include Sprint velocity (delivered points), Churn rate, Commit done points etc. Find the complete list of supported Sprint Metrics here.
Sprint metrics ratios
In addition to the individual metrics, there are mathematical ratios that provide insights into the team's performance and efficiency during the sprint. These ratios are calculated based on the existing sprint metrics.
Find the complete list of Sprint Metrics ratios here.
Create a Sprint metrics Insight
Having a Sprint Insight can help address issues related to the sprint success and enhance the overall sprint planning and delivery process. Refer to the below tutorial to learn how to create an Insight (i.e. Dashboard) configured with the most frequently used Sprint metrics reports to measure your team's contribution and activity across various sprint cycles.
Best Practices and Recommendations
Improving Sprint Metrics reporting
Apply appropriate Filters to ensure that the widget displays data relevant to your team's sprints or projects. This will help you analyze the right set of data for your team.
Choose the sprint metrics that are most important for your team's goals and objectives. Different metrics provide insights into different aspects of your sprint performance, such as commitment, scope creep, and delivery.
Configure the Aggregation settings (e.g., by sprint, weekly, or monthly) to align with your team's sprint cadence and reporting needs. This will help you identify trends and patterns more effectively.
Customize the widget settings to your team's specific processes and conventions. For example, define the Sprint Creep Grace Period and Additional Done Statuses to accurately reflect your team's workflow.
Maintaining Issue Hygiene
Ensure that all team members consistently use the correct status fields in the issue management system when updating tickets. The platform relies on specific status values (e.g., Done) to calculate completed work accurately.
When making changes to sprints, such as adding, removing, or re-estimating issues, ensure that these changes are accurately reflected in SEI by configuring the widget settings. Failing to do so can lead to discrepancies between the committed and delivered metrics displayed in the widgets.
Last updated
