I know that this is not good agile practice, but we have a significant percentage of stories which are not complete at the end of a sprint. To calculate capacity needed, the teams usually reduce the story points from the original estimate to the remaining story points.
Example: original estimate 10 story points, at the end of sprint 5 the story is almost done and will require 2 more story points to complete, so the story point field is changed to 2 for sprint 6.
However, we realized that this distorts our story point reports, because once the story is complete, only the revised story points will be credited, and the velocity of the team is too low.
Is there a way to distinguish between "completed" and "remaining" story points? So in the case above, 8 story points would be credited to sprint 5, and 2 to sprint 6?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events