JIRA sprint planning - best way to re-plan after leaking?

Juha Välimäki November 18, 2021

Hi,

I have made couple of sprints long plan. Now there are leaked items which make a collateral effect on the following sprints. What would be the best way to re-plan (tooling-wise) without needing to go thru ticket by ticket and move them accordingly.

Some kind of batch operation to move all the tickets e.g. +1 sprint?

I have Advanced roadmap in use, if that helps.

1 answer

1 vote
Kit Friend
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 18, 2021

To be honest this should be actively replanned by the Product Owner, not just shifted by a tool

Juha Välimäki November 19, 2021

Actually, it should be done by the team, not PO. I am just seeking options to make that easier.

Kit Friend
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 31, 2022

Well Product Backlog Prioritisation at a chunky level = PO, the team needs to agree  into inclusion in each Sprint backlog and breakdown if they wish into tasks (assuming we're doing Scrum) right? :)

When closing a Sprint Jira will automatically give the prompt on what to do with the hanging over stories, and in the backlog view you can multi-select and move tickets. 

Juha Valimaki February 2, 2022

Well, you were talking about replanning, not prioritization. I agree PO is to be making the prioritization in the end (using team input).

 

Closing sprint will prompt yes, and you can choose to move the items, but I was more after way to move selected items distributed several sprint e.g. +one sprint as there is collateral effect.

Suggest an answer

Log in or Sign up to answer