The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Sprint Planning: See next sprint as a board, not just a backlog?

ToBe
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 18, 2016

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?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Deleted user
October 19, 2016

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.