I have an 8-point story. Four points were completed and I need to roll it over into the next sprint. In the next sprint I will complete the last four points. Normally, when I close the story in the new sprint, Jira shows that all points were completed in the new sprint, vice the last four points. If I use the time tracking feature, and roll the story over, will Jira reflect the fact that eight points were completed over the course of two sprints?
Hello @Breeze
No, Jira does not give you credit partially completed work. All points on the item are credited to the sprint in which the issues is completed. The issue must be in a "complete" status (right-most column of the board) at the end of the sprint to be considered completed in that sprint, and all the points associated with the issue are then considered complete in that sprint.
Generally the idea of scrum is that you are committing to completing all the work for the issues you add to the sprint. If you don't think you can complete all the work for an 8 point story based on your resources and your other commitments for the sprint, then you should break the story into smaller issues that you can complete or plan to commit to that that story in a future sprint.
Seeing in your sprint reports that you had committed to completing those 8 points but did not do so is an opportunity to review your estimation process, sprint planning process, and sprint execution process. Why was the story not completed? Was the work under estimated? Did you over commit to what you could complete, given the available team members? Did some unexpected work divert you from the work to which you committed? Was there an unexpected reduction in the number of available team members of the time they could apply to working on sprint items.
Use the discrepancy between your committed points and your completed points to improve your process.
Came to these forums for basically the same question as Breeze and as usual @Trudy Claspill makes some great points.
Can I separate Completed Points from Sprint to Sprint?
Any way you break down a large ticket at the end of a Sprint ultimately is at the most basic, planning smaller issues exactly as Trudy suggest should happen upfront.
--
It's something I am still preaching to my wider Prod dept too. Some day I hope they will see it's the same effort, just better planning to do it upfront.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.