We use a Scrum board with final status = Done (Set Resolution)
When the sprint is complete, we need those tickets to move to a Kanban board for User Acceptance Testing. How can we achieve this?
well it depends on your workflow TBH. If "Done" status ultimately goes to subsequent statuses, e.g. UAT which then can say move to "Closed" then you can certainly do this and I have done something similar before (see below). Now if Done is in fact the final terminal state then this wouldn't make sense as you couldn't transition to final closure.
Example solution:
assume you have a workflow that looks like this - To Do > In Progress > Done > UAT > Closed
then you might have...
Workflow status for development: To Do, In Progress, Done
Workflow statuses for QA: UAT > Closed (can transition from UAT back to To Do or other if it fails)
Now for the boards:
Dev Scrum board JQL - project = xxx and status not in (UAT, Closed)
QA Kanban board JQL - project = xxx and status in (Done, UAT, Closed)
so you see that "Done" will be on both boards. It will be the right-most in the Dev Scrum and the left-most in the Kanban. Done equates to 'to do' for the QA phase and hence belongs on the left.
Does your example still provide for generating metric for tickets when the Sprint is closed, "Done"? That's one of the issues I'm having trying to figure this out.
UAT is completely separate from the Scrum, so tickets will remain on the Kanban board until it's scheduled and complete. Available UAT tickets are based on tickets that are "Done" from Sprints.
yes it should since scrum boards base the metrics off the right-hand most column. I would likely consider a more complex "resolution" implementation, e.g. when moved to Done set the Resolution to say "Dev-complete" and then when moved to Closed to maybe "resolved, complete, done, etc.".
yes the boards overlap w/ Done, e.g.
Scrum - To Do >> In Progress >> Done
Kanban- Done >> UAT >> Closed
Thank you for your time and responses.
I will give this a try in the morning and report back.
Another option to consider is to use automation to create a new task altogether when an issue is moved to Done w/ a specific resolution that indicates it is ready to be tested. You can use smartvalues to pull in the triggering issue's summary, etc. and link the two. Personally, I prefer separate issues as it retains some since of ownership. You could even have the original issue 'reopen' if the QA issue is transition to 'failed'.
just a thought.
It looks like you're new here. Sign in or register to get started.
