Details
-
Suggestion
-
Resolution: Fixed
-
None
Description
Raised on behalf of a customer.
We're scheduling a Sprint with x Story Points, however due to scope change during the sprint we end up completing only y. During the sprint we change some Story Point values on the stories to account for new stories being added after the sprint has started and it's a way of indicating how much work we actually completed on the story. We work in a small company, so there is often a lot of scope change for last minute requests on work.
At the end of the sprint, we need to see how much work we actually completed, rather than what we committed to. The Sprint, Burndown and Velocity Report all display committed story points rather than story points after scope change.