We started this Scrum foundation series explaining we see four underlying concepts of the Scrum framework. In the past series of mails we covered the three pillars of Empiricism, the Scrum Values, and a Self-Managing and Cross-Functional Team.
The concept Done is the fourth of these concepts. It needs a self-managing, and especially a cross-functional team, a team living the Scrum Values, to make it work in a way that it brings the needed transparency with regards to the quality of your solution/product.
👉 A solution (Product/Increment/Service) the team labels as Done, meaning the solution meets the required quality measures, is ready to be released in the hands of the users, in their day-to-day life.
Being Done = meeting the required quality measures = a new Increment exists = a production release is possible.
Done should receive the necessary attention by each of the Scrum Accountabilities.
Given the Developers are accountable to instilling quality by adhering to a Definition of Done, Done is a key concept for them. This is really their accountability!
So what can Developers focus on?
During Sprint Planning, come up with a plan that makes it clear how the Increment will meet its Definition of Done.
During the Daily Scrum keep focussing on finishing Product Backlog Items (PBIs) – finishing meaning these PBIs are fully integrated in a Done Increment.
During the Sprint Review, only show PBIs that are completely Done so that attendees can trust what they see and when they use is the new Increment it is of their expected quality level.
During the Sprint Retrospective evaluate 1/ how to make it easier getting to Done, and 2/ how quality can be improved by adapting the Definition of Done.
These are just a few examples.
To the Developers, the Definition of Done is their quality goal. When it comes to inspecting the Increment, Developers look for any undesired deviations between the already realised quality level and the expected quality level.
When it comes to Done, the Developers are the Scrum Team members that do ensure the Increment meets the agreed Definition of Done. Continuous attention to it is expected from them.
Together with your Scrum Team, evaluate how the Developers can be more effective in reaching the agreed Definition of Done each and every Sprint, and how to keep improving it.
We hope you will find value in these short posts and if you are looking for more clarifications, feel free to take contact.
PS. Next week we’ll look at the use of Done and the Scrum Master.
If you want to take a deeper dive into the core concepts we are covering in this blog series, then surely check out our Professional Scrum MasterY workshop. We have some scheduled in the coming period.
Don’t want to miss any of these blog posts? Have the professional Scrum foundations series weekly in your mailbox.