Why with Agile 2.0 does it add additional story points to the Total Points commited to the sprint when you move a new story in?

Angie Plagman
Kilo Contributor

The total committed points field in the old Agile module in SN locked down once you committed to the sprint, so the total number of committed points never changed. 

 We've upgraded to Agile 2.0 as well as Madrid and now it changes the total committed points every time a story is added to the sprint, even after the sprint points were committed to.

 

Ex:

6/15 we do sprint planning and the Total committed points show 600.  The state on the sprint is changed to current and the sprint begins.

6/18 A developer pulls in a story that wasn’t considered during sprint planning and was NOT included in the total committed points equaling 600 but it adds the 16 points in to the Total committed points.

 

Can anyone explain why this change would occur?  We are trying to do metrics on our sprints and it's complicated when your Total committed to sprint changes throughout the sprint.  We feel the Total committed to should remain the same and the new story should only be added to the completed points at the end of the sprint (if it applies).              

 

1 ACCEPTED SOLUTION

Thom12
ServiceNow Employee
ServiceNow Employee

Angie, this has been changed in New York. The Total Committed Points field will work as it did in Agile Dev 1.0. Once you start a sprint, that value is recorded then remains unchanged regardless of whether you add new stories, remove existing stories, or change the estimate on existing stories. During the course of the sprint, the following two field values can change: 

  • Current Scope Points gives the total of the work currently scheduled in the sprint. This value will change as new stories are added, existing stories are removed, or existing stories are re-estimated. 
  • Completed Points gives the total of the work completed in the sprint. 

Hope this helps! 

View solution in original post

3 REPLIES 3

Brian Lancaster
Tera Sage

My thought would be that if you add additional work to a sprint your point would change because of that.  It could possibly be a bug in Madrid as well so you my want to reach out to HI and create a case if this is not the expected results.

Thom12
ServiceNow Employee
ServiceNow Employee

Angie, this has been changed in New York. The Total Committed Points field will work as it did in Agile Dev 1.0. Once you start a sprint, that value is recorded then remains unchanged regardless of whether you add new stories, remove existing stories, or change the estimate on existing stories. During the course of the sprint, the following two field values can change: 

  • Current Scope Points gives the total of the work currently scheduled in the sprint. This value will change as new stories are added, existing stories are removed, or existing stories are re-estimated. 
  • Completed Points gives the total of the work completed in the sprint. 

Hope this helps! 

Thanks for your help!  I've let our team know.