Is there a way to split the done column into 2. A done part for tickets that are complete and a ready for release part for tickets that still require testing but essentially the work is done? We currently have a ready for release column where "dev completed" work lives but it's not done done as it hasn't been through regression testing yet and regression testing happens after all sprints are complete within a release cycle (currently 4 sprints per release).
You can have two statuses 'done' and 'done done'. However, for scrum boards only the right most column will be processed as done. All other issues including those in 'done' will go back to backlog on completion of sprint.
Hi @Jack Brickey - I'm curious to know what's the best practice to show the items that are "releasable" (aka dev completed, QA/UAT'ed) in the burndown chart.... and how you would use the board to present what's releasable (done) and released (done done).
Would you map both 'done' and 'done done' status in the right most column? Or leave the 'done done' status as unmapped?
FYI @Andrea Smart
If you wish to manage deployment separate from development complete issues and you want to leverage scrum for development you might wish to consider two boards.
this allows you to have the dev team separate from the deployment team/decisions
of course this really depends on understanding your process and how are you and your team work.
I really like the concept of separating development activities from deployment activities with 2 separate boards.
How would you set it up to be able to transition a ticket from the Done, or Ready for Deployment, state on a team board to the Ready for Deployment state on a shared Kanban board in a scenario where you have 3 team boards and a shared deployment Kanban?
I think that makes sense. So the last column on each board represents 'Done', correct? In that scenario would I be able to track a ticket's total cycle time through all 3 boards?
It looks like you're new here. Sign in or register to get started.
