Deployment of issues not being deployed after each sprint

[Shari Fitz-Patrick]

We do not deploy code after each sprint so therefore Issues in the 'Ready for Deployment' column could sit there for a number of sprints.  I was going to change the definition of DONE to Product Owner Review.  That leaves me with two columns Approved for Deployment and On Pre-Production.  What would you recommend we do with these issues as they could sit around for a number of weeks.  

[Jack Brickey]

Here is my suggestion it may or may not work for you but it has for me in the past. You will have two boards a scrum board for the development that would end with ready for deployment right most column. The second kanban board would be used for deployment it would begin with ready for deployment and end with done in the right most column. And this way your development scrum board will be nice and clean and the kanban board provides the flexibility of deploying code as appropriate.

[Shari Fitz-Patrick]

Thank you.  I actually tried that out before receiving your answer.  I am pleased to see that you recommend the same thing. I do have one more question.  Is there a way that the issues that are in the first board with the status ready for deployment could then be automatically moved to the second board with the status of ready for deployment?

[Jack Brickey]

Yes. In fact that is how I would recommend it. Basically, you would have that status as the last column in your dev and the first of your deployment board.in this way there is a desirable overlap.