Say you finished your last sprint and not everything was finished. So, when closing the last sprint, the open tickets move to the next sprint in whatever status they're in.
Right now, our sprint backlog shows story points and the sum of that.
To properly assess what's left for the next sprint, we don't plan on reevaluating the story point estimate for unfinished stories. These are to always reflect the original estimate for the story.
In order to assess how much and what is in which state on the next sprint's board before it's even started, how can we look at it as a sprint board before we go and start the sprint, in order to better assess how much room there really is?
Well I have a few suggestions;
To use a board based approach, build a Kanban board (Sprint board will not work). Update the filter for the board to show those issues assigned to the next Sprint + unfinished issues from the previous Sprint. Setup your columns just like the Sprint board.
You could also use an Issues report with the query setup like the filter above.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs