It feels great to say something is done.
(Double the fun when you can also move your task to a Done column)
But after getting feedback, a lot of times we learn that our work was not as done as we thought it was.
Killing for morale, and also disrupting the next task you are working on.
Three things are causing this:
There's an example checklist below for you to use in your team, but first let's look a some examples.
With a "Definition of Done" checklist, the quality of your team's work will always follow high standards. It works because you have agreed as a team what those quality standards should be.
It's like having a chef in your kitchen who checks your next meal before leaving the kitchen. But for teams.
Plus, the only thing you need to make it work is to tick the boxes of a checklist before saying something is done…
Curious to know how?
Before moving your next task to Done, make sure you tick off all the boxes of your Definition of Done checklist ✅.
Always be strict about your team's Definition of Done.
Here are 3 simple steps to implement a "Definition of Done" for your team:
A Definition of Done example for your team can be:
Need to convince your team to give this a try?
Alright, let's say your team is "finishing" 40 tasks per week and 10% of that is undone (aka moved back from Done to Doing). That means finishing 160 tasks less per year (even without calculating the productivity hit on your next tasks).
I have seen teams double in productivity because of the Definition of Done.
Also, as your team matures your Definition of Done will include higher quality standards.
Not bad for a checklist.