This trio of metrics is a great addition to any dashboard looking at any number of teams that work with Sprints. Data for all previously completed sprints will be available and filtered by the date picker in the top right (default 12 weeks).

The completion rate is calculated as:

Here are some quick definitions of each metric:

Sprint target completion - Percentage of tickets completed within a sprint from the tickets that started the sprint.

Sprint work added completion - Percentage of tickets completed within a sprint from the tickets that were added to the sprint after it started.

Sprint completion - Percentage of tickets completed within a sprint from the tickets that either started the sprint or were added to the sprint after it started (i.e. a combination of the first two).

Understanding Ticket Outcomes

The initial metric will display the completion percentage of each sprint based on the definitions above, but for more details, you can click the BY TICKET OUTCOME tab above the chart. This will now break the outcome of each ticket into 4 mutually exclusive categories.

Completed tickets - completed before the end date/time of the sprint

Incomplete tickets - not completed before the end date/time of the sprint

Closed incomplete tickets - completed with a negative status or resolution (if using Jira). i.e. "Won't Do", "Duplicate" etc.

Removed tickets - unassigned the sprint before the end date/time of the sprint

Calculation

Unit of Measurement

Although the default Unit of Measurement is ticket count, this can be overridden with alternatives. The most common being Story Points. This will do everything above, use Story Points in the calculations rather than ticket count.

Sprint End vs Completed Date

Within the calculation settings, there is also an option to choose the sprint date field that represents the finish of your sprints. The End date is the original planned finish date, whereas the Completed date is the actual finish of the sprint when Complete Sprint is clicked in Jira.

For ticket data from Azure DevOps, this setting will make no difference to the data as only one 'finish' date exists.

The default value used when adding this metric to a dashboard will be based on an organisation-wide setting that is in place for your instance of Plandek. If you want to know more, please contact us.

Example

The below sprint is started, with the End date set to 20th April 2021 08:53 (the time is used in our calculation).

On the day of the 20th April the team still have 5 final tickets to finish and move to Done. They complete these in the morning, and at 2pm the Scrum Master clicks Complete Sprint. The Completed Date is now set to 20th April 2021 14:00. Within Plandek when End Date is selected the 5 final tickets will show as Incomplete, but when Completed Date is selected the 5 final tickets will show as Complete (for the given sprint).

Filters

Due to the nature and complexity of Sprint completion, there are far fewer filters on offer. Critically, however, you have the ability to filter in Issue Types.

Here you might want to limit the metric to Stories and Bugs, excluding Sub-tasks. Ensuring that you are counting the right tickets to base the completion rates on:

Did this answer your question?