We created a new status in our workflow called "DOR". This means that the User Story meets the "Definition of Ready" and we want that only issues in this status can be added to our sprint.
Our workflow looks like this:
Open -> DOR -> In Progress -> Testing -> Pre -> Done
Obviously we need the status "Open" in this board so that the POs are able to see issues in their backlog after they were created.
We are already forcing the workflow to go trough the status "DOR" but we want to avoid that people add the issues to their sprint first, start the sprint and only after this move the issues to the "DOR".
How can we do this?
Hello @Markus
The easy way of implementing your requirement is to have two separate boards (that's how I do as well )
One PO board and other Dev Scrum board.
The PO board will have statuses Open -> DOR in their Kanban board and once they move the issues to DOR only then the issues appear in the backlog view of the Dev Scrum Board so that now the team can pick the issues which are actually reviewed by the POs. In the underlying filter of the Dev scrum board you can easily exclude the issues in the open status as these issues belong to the PO board.
Hey,
You can also change the filter of the board? Is that help in your case?
Like Project="XYZ" and status in (DOR)
(By doing that you won't be seing the open ones)
Edit: If your PO want to see the open ones, maybe they can create another board for that, or just a dashboard
Cheers,
Ege Su
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That would restrict the board to only show DOR tickets and if they move the issue during the sprint, they would lose it.
So instead a more appropriate filter would be status in (All other statuses) or as suggested by @Tarun Sapra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Markus,
I am not aware of how you could do this if all other statuses are still present.
I would recommend having a defined sprint master and deputy and they would be the only ones who add issues to sprints. (Manual but this works).
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.