What is the best solution for creating a separate section for Ready-for-Deployment issues in Scrum?

Question

Dear Community,

I need your expertise in figuring out how to separate some of the issues that have Ready for Deployment status and do not interact directly with the current(active) sprint backlog.

So here is the scenario. We have decided to do product updates twice per month and all those issues which reach the status of Ready for Deployment are deployed to the production (master branch) on a specific date. As I have mentioned this happens twice per month. As a result, we happen to have 1-10 Ready for Deployment issues that roll over to the next sprint when the deployment is scheduled. Ready for Deployment issues are the ones that have been already tested and are awaiting their time for deployment. However, by rolling them to the next sprint, often the active sprint log becomes very long and kind of inconvenient to handle the process effectively. So they are just ready issues waiting for their time to be pushed to production.

Ideally, I would like to have a sprint where ready for deployment issues are PART OF THE CURRENT SPRINT HOWEVER THEY DON'T appear among the active sprint issues. I would like to know if you have a similar practice and how you have dealt with this situation. Is a parallel sprint solution something that I can opt for? Or there is another way to create a vault for ready-for-deployment issues which are not visible among the active issues.

Hope this is clear what I want to know.

Regards,

Vahan

Nic Brough -Adaptavist- · Answer

Go to board configuration -> columns and drag the status from its current column to the last one.

Vahan Alaverdyan · Answer

Thank you for your answer. Could you show/tell me how to map the "ready to deploy" status into the "done" column? Much appreciated!

Nic Brough -Adaptavist- · Answer

It sounds like your "ready for deployment" issues are not really sprint items, as you are not planning to complete them as part of a sprint, and neither are they completable within one sprint.

I'd either remove them from the planning and the board completely, treat them as external tasks for their entire lifecycle, or if you do need to treat them as sprintable items for part of their life, map the "ready to deploy" status into the "done" column, so they don't mess up your numbers.