Creating multiple boards or using fake sprints which is better

[StepwithSJ]

In my team they don’t close sprints so now I am cleaning up to close them but issue is lots of tickets are in ready for release status and they will get released in future sprints . So to close them I either have to move them to future sprints or to backlog. But problem is if it goes to future sprint the velocity/capacity of that sprint will not be correct and if it’s moved to backlog then it might get lost as the backlog is huge.

so I thought maybe if I create a fake sprint where only ready for release tickets can be kept and when they can be released I can move them to appropriate sprint . Is this better or should I create another board with filter for status and use that backlog to track.

please suggest what is better. Thank you.

[Bill Sheboy]

Hi @StepwithSJ -- Welcome to the Atlassian Community!

Based on your statement that your team doesn't close sprints, I recommend pausing and...

• meet with your entire team, scrum master / agile coach, and product owner to review fundamentals of methods such as Scrum
• discuss the purpose / value of a team measuring something like velocity
• discuss why the team is not closing sprints
• discuss why work does not finish during sprints
• discuss how the team does release management, and how that fits with the team's use of Scrum
• discuss experiments to try and improve their working methods

Kind regards,
Bill

[StepwithSJ]

Thank you @Bill Sheboy . I did have a meeting with team and therefore I am working on closing the sprints now . The issue is here it is 5 days sprint and release happens every week but there are always some tickets left from the sprints which are part of some epics which will be released later. Due to this those tickets just stay in the sprints without getting released till the epic is planned to be released. 

[Bill Sheboy]

I have observed that situation when releasing is independent of building a feature.  Some solutions for that are smaller release chunks (to reduce bundling), and / or the use of feature toggles so code can release but not be accessible to customers yet...allowing enabling the component parts of the feature all at once, etc.

[Varsha Joshi]

Hi @StepwithSJ 

I would use a separate board and manage all your ready for tests issues there. It is easier to view and share it with others without cluttering your existing sprints in a given project.

Hope this helps.

-Varsha

[StepwithSJ]

Thank you @Varsha Joshi . I have created a separate board to see how it helps but my concern is will it be a tedious way for product owners to track