re: Should blockers be part of the Definition of Done? VIEW POST


A very simple approach you can have when it comes to consolidating what "Done" means to your team is:
Is the original issue/struggle solved with what we're delivering?

With that in mind, it becomes clear that no, it is not done.

Also, remember that a blocker blocks, which means that in your development process from "To Do" to "Done", if there is a blocker, the story never reached done, because it's blocked.


I like your suggested approach/question.
An alternative could be "Is our product acceptably shippable even with this issue?".

Thanks for the input.


That makes sense, it's a different context than the one I'm into (we ship on demand, not product oriented), but I guess the principle remains.

Glad I could help :)

Code of Conduct Report abuse