-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: documentation
-
None
-
1
Issue Summary
The customers bring up the issue as the different values are shown in a lot of Jira Align reports. We find Jira and Jira Align has different definitions for committed/commitment and the customer suggest calling out the distinction in Jira Align reports, such as :
- Sprint Coaching
- Sprint Metrics
- Sprint status
- Points Planned vs Points Accepted etc
Details/ History
Jira and Jira Align has different definitions for committed/commitment. Information in our documentation does indicate that JA Committed Points may not be equal to the Jira Commitment, as Jira bases this information on the start of the sprint, where Jira Align can change the information depending on the history of changes to stories within the Sprint
From the bug JIRAALIGN-3128, PM team provide the information as follows;
"The Committed Plan: All values in this section are calculated prior to the start of the sprint. After a sprint has begun, removing a story or story points will not reduce a value."
In our reports, this general rule applies:
• "Committed" refers to values that measure stories that are planned PRIOR to the sprint start date.
• "Planned" refers to values that measure stories that are planned ANYTIME in the sprint – prior, during, or after the sprint start/end dates.
In Jira there is no differentiation between committed & planned story points i.e. Jira considers both as one and the same. The story points before the sprint starts in Jira equals to what is the teams' commitment (or planned).
for example, In View and understand the velocity chart, we describe the Commitment statistic for in the Jira Velocity Chart as:
The gray bar for each sprint shows the total estimate of all issues in the sprint when it begins. After the sprint has started, any stories added to the sprint, or any changes made to estimates, will not be included in this total.
- relates to
-
ALIGNSP-12558 Loading...