I'm looking for some advice or suggestions as to the optimal approach for partially complete rollover stories and velocity calculation.
Let's say a developer picks up a 5 point story near the end of Sprint 1. At the end of the sprint, they estimate that they have completed 2 out of the 5 points. However, when the sprint is ended, the story (and all 5 of it's points) will be moved in to Sprint 2. Assuming this is the only story in Sprint 1 the velocity for this developer according to JIRA will be:
This is causing the following problems
You have misunderstood what scrum estimation is for and how it works.
The mistake here is "partially complete rollover" - this is nonsense and does not exist in Scrum. When you bring an item into a sprint, you are committing to completing it in that sprint. At the end of the sprint, the item is either done or is not.
If an item is say 5 story points, it doesn't matter if you think you've got 1 point in or 4, you can't tell your product owners that it is done.
The way to "fix" this is to use the estimates as intended:
Yep this makes sense. It's the right way to do it for sure. Was curious if JIRA supported the wrong way to do it as well. No matter, we'll continue to get better at capacity planning outside of JIRA (in spreadsheets) so we don't take on as much work, and JIRA works as designed.
Solution tl;dr: Work to get better at planning sprints to reduce rollover and then the JIRA rules around sprints and calculating story points (velocity/burndown) will work for you.
I agree with Nic.
JIRA was not designed to be a SP tracker. You use the team's SP velocity (totals SP per sprint trend over time) and actual SP budget (adjusted for people on leave during next sprint, etc) to determine how many SPs can be loaded. The total SPs per sprint is to help the team understand what they can realistically complete during the sprint.
If the team cannot finish the agreed total SPs by the end of the sprint, then Nic has identified the ways to address this problem for the next sprint.
After several sprints, the team will find the most realistic number of SPs which can be loaded.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
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