Story completion ratio

About this report

The Story Completion Ratio Report provides an overview of team performance, relative to the total, committed and percentage complete for all stories, across a user-definable scope of 3, 5 or 10 sprints.

The report gets its name from displaying a line graph showing committed stories and completed stories for each sprint, as well the expected range for consistent delivery. The generated graph is especially useful for Team Members, Product Owners and Scrum Masters to understand how consistently the team is estimating and delivering against their sprint commitments over time.

Users may select a time window of 3, 5, or 10 sprints to be displayed on the chart's horizontal axis from the Extra Configs menu. The vertical axis displays the percentage of stories completed on the left-hand side of the chart. These percentages are displayed as decimal values only (e.g. 0.6 = 60%).

Another standard feature of the graph are red, yellow, and green lines, reflecting Jira Align Administrator selected thresholds at 60% (red), 75% (yellow) and 90% (green), by default. Jira Align Administrators can adjust these thresholds globally. Committed and Completed Stories (blue and black lines, respectively) will fall above or below the predefined thresholds. 

Hovering over points on the graph will display flags that indicate the significance of each item.

Navigation

1. Select the Reports icon from the left Navigation menu.
2. Start typing the report's name in the Search box. 
3. Once found, select the report.

Note: You can also use the categories on the left to search for the needed reports.

Prerequisites

1. A Product must be defined in the system and be tied to a program.
2. A sprinting Team must be selected with stories within the last 3, 5, or 10 sprints. 
3. Stories, with point values, must be created and assigned to features within the program.
   
   

How are report values calculated? 

1. Committed Stories = Count of committed stories at the end of a sprint planning meeting or stories loaded into a sprint as of 11:59 PM on its first day if a planning meeting wasn’t run.
2. Completed Stories = Count of stories accepted by the end of the sprint.
3. Story Points = Percent of stories completed.

How to interpret this report

Teams delivering with consistent velocity should have committed and completed story lines that fall within the narrow band between the orange and green lines depicted on the graph above. Teams should strive to stay above the low threshold (Red or Orange Line) established by your organization (60% as depicted above). While over-achievement can be viewed as a positive thing, staying below the Green line is a best practice as reserving capacity for quality, technical debt or other infrastructure-based activities should be a standard part of Sprint Planning.