Purpose
Commitment Rate shows the amount of work planned vs. completed, in %. In Scaled Agile Framework (SAFe) a similar metric is called a Program Predictability Measure.
How metric helps
Commitment Rate helps to determine a team "reliability" and to accurately estimate the amount of work a team is able to deliver in future iterations.
Questions it answers:
how stable is the performance of a team
does team keeps their commitments
how stable is the reliability of a delivery process
Benefits: Get confidence that
current workload the team fits team's capacity
sprint planning is properly organized based on delivery plan and dependencies
provided estimates are accurate enough to rely on
delivery is on time
How metric works
Chart overview
Chart displays the ratio between planned and completed amount of work in % with the following variations:
Types of Iterations -
Sprints
Releases
Types of measuring -
amount of work items
in Story Points
in man-hours (Remaining Work)
in man-hours (Original Estimate)
Axis X - iteration name/timeline; Axis Y - completion ratio.
On hover over a column, a hint appears with the following information:
Iteration name - Iteration name as it is in a tracking system, e.g. sprint title in JIRA;
Iteration time frame - Iteration start-end date;
Committed - number/story points/hours of committed items;
Completed - number/story points/hours of completed items;
Rate - Committed/Completed in %.
Drill down includes the following:
Issue ID;
Type;
Priority;
Summary.
Calculation
Commitment Rate = Ncompleted / Ncommitted * 100 %,
where
Ncompleted is a number of issues got a 'Done' status before or on the sprint end date and time.
Ncommitted is as a number of issues assigned to a sprint before or on the sprint start date and time plus Sprint Planning Grace Period (set in Project Settings>Data Sources>Task Tracking system >Scope Management>Sprint Planning Grace Period).
Calculation | Items | Story Points | Original Hours | Remaining hours |
Committed | a number of issues assigned to a sprint before or on the sprint start date and time plus Sprint Planning Grace Period | sum of SP for issues assigned to a sprint before or on the sprint start date and time plus Sprint Planning Grace Period | sum of Original Hours for issues assigned to a sprint before or on the sprint start date and time plus Sprint Planning Grace Period | sum of Remaining Hours for issues got a 'Done' status before or on the sprint end date/time. |
Completed | a number of issues got a 'Done' status before or on the sprint end date/time. | sum of SP for issues got a 'Done' status before or on the sprint end date/time. | sum of Original Hours for issues got a 'Done' status before or on the sprint end date/time. | sum of Remaining Hours for issues got a 'Done' status before or on the sprint end date/time. |
RAG thresholds: Green - metric value > 80 % and <100 %; Amber - metric value <=80 %.
Calculation notes
Sprint Planning Grace Period is set in Project Settings>Data Sources>Task Tracking system >Scope Management>Sprint Planning Grace Period.
'Done' statuses are specified in Project Configuration>Data Sources>Task Tracking system >Workflows.
Committed issues moved to another sprint are counted in the sprint they are actually completed.
Issues/work items got into a sprint after a sprint start and completed within this sprint are included into Completed.
Reopened and completed issues are included in the completed value calculation by their latest completion date timestamp.
Estimates for Committed are taken at a sprint start including a grace period value if any.
Estimates for Completed are taken at an issue completion.
Sub-bugs and sub-tasks are NOT taken into the calculation in items.
Calculation of the metrics based on TFS takes into account sprint start at 23:59:59 so the same metric based on Jira data may differ.
Releases without start/end dates are ignored.
Trend line (blue dotted line) calculation (its inclination to axis x) ignores an incomplete iteration in the chart to reveal an accurate tendency.
Data Source
Data for the metric can be collected from a task tracking system (Jira, TFS, Rally, etc.).
See also
Copyright © 2024 EPAM Systems, Inc. |
|---|
All Rights Reserved. All information contained herein is, and remains the property of EPAM Systems, Inc. and/or its suppliers and is protected by international intellectual property law. Dissemination of this information or reproduction of this material is strictly forbidden, unless prior written permission is obtained from EPAM Systems, Inc. |