"Is it Done? The common answer would be: Kind of Done, nearly Done!”
With that in mind, have you discussed what defines a ‘Done’ item with your Team?
Here is why you should consider creating a shared and solid « Definition of Done’: DoD:
🤝 Transparency regarding the team’s process :
A shared DoD lists all the activities that the team should do to get an item to the ‘Done status’ including technical reviews, unit testing, functional validation or documentation if necessary.
📈 Transparency regarding the Product Increment :
No surprises! All the features shown during the Sprint Review should be part of the Increment and ensure the quality criteria defined in the agreed DoD; so that the Product Owner can plan his releases with confidence.
📍 Transparency about where we are:
When the definition of what is Done and what is not is clear, you can communicate clearly about your progress and your product owner can easily update his stakeholders about possible releases’ dates or potential problems ahead of time.
🗺️ Transparency about where we are going:
The team can estimate the size and complexity of their backlog items easily against a known and agreed DoD; This would help forecasting upcoming similar work too.
🔄 Transparency about planning a sprint:
The sprint planning will be smoother when the team is confident and clear about the amount of work that has to be done to complete any piece of work
In an upcoming article, I will walk you through practical steps to create yours DoD !
P.S – If you found this useful, please repost, like & follow our page or Abir Mejri, our Agile coach for more insights !
#5benefitsDoD #ScrumGuide #DoD #TeamWork #PerformingTeams #Scrum #Agile #Transparency
