minimalizing future sprints

Anne van Susteren-Finger

Hi,

 

We see a lot of teams who create multiple sprints for the rest of the year or the next year. But the conclusion is that in the backlog from the scrumboard gets pretty overwhelmed by all the future sprints.

 

The question in here is, if there is a option to minimalize the future sprints in the backlog. They are still there but not fully visable. We would like to know if this is possible. Or if there is a work around for this?

Walter Buggenhout

Hi @Anne van Susteren-Finger and welcome to the Community!

That is a very valid point. If there's too many sprints in the backlog, it becomes quite difficult to see the actual work.

Jira does not let you filter away sprints. As a best practice, talk to your teams and advise them not to do this. Sprints are designed to plan ahead in short cycles (most commonly of 2 weeks, but teams are free to specify any length they prefer). As you will see, it is already difficult enough for most teams to complete the work they commit to within this short timeframe, let alone that they would try to plan ahead for an entire year. They will find themselves moving stuff across multiple sprints the entire time, losing the benefit of a flat list of items ready to be picked up.

Since Jira suggests the name of a new sprint automatically from the last sprint name on the board, creating a new sprint is usually very quickly done. I would recommend not to plan / create more than 2 or 3 sprints ahead of time.

Hope this helps!