blog

Getting started with a Definition of Done (DoD)

Published on
8 minute read

In my last post about Professional software teams creating working software  David Corbin  made a good point. How do you determining what “Free from fault or defect” means? Since that is different for each Product and may change over time you need to focus on Quality and reflecting that quality in a Definition of Done (DoD).

Updated to reflect the 2020 Scrum Guide! 

TL;DR;

Your Developers are ultimately responsible for creating done increments of working software. Done Increments. Done.

Getting started with a Definition of Done (DoD)

Developers needs to decide what Done means within the organisational context and the product domain. They need to sit down and create a list of things that must be true for every Increment of software that they deliver. Working Software is not specific to a PBI; it’s applied regardless of PBI to the entire delivery. Not just for each PBI.

“The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product Backlog for future consideration.”

- The 2020 Scrum Guide 

If you can’t ship working software at least every 30 days then by its very definition, you are not yet doing Scrum. Since Professional Scrum Teams build software that works , stop, create a working increment of software that meets your definition of done (DoD), and then start Sprinting, and review what you mean by “working” continuously, and at least on a regular cadence.

What is a Definition of Done (DoD)

You need to start somewhere, and most often we don’t have a greenfield product. Either we are handed an existing product, or we are the team that built it and are switching to Scrum. Wherever your product originated, the code, and thus the product, will not currently be working software. How can it be when you don’t have a definition of what working means? So what do you do?

Before you cut a single line of code, you need to decide what done means for your product and your company. It will be defined very differently if you are building firmware for pacemakers or if you are creating an e-commerce portal. Here are some characteristics of a Definition of Done:

Your short, measurable checklist that mirrors usable and results in no further work required to ship your product needs to be defined. I find the best way to do this is to get the Scrum Team  (the Product Owner plus the Developers  and any relevant Stakeholders  ) into a facilitated DoD Workshop  . Without a Defenition of Done we don’t understand what working software means, and without working software we cant have predictable delivery  . Your Product Owner can’t reject a Backlog Item  , only whether the Increment is working or not.

My first Definition of Done (DoD)

Your Definition of Done  does not just magically appear, and your software does not magically comply. Making your Software comply with your definition of done is hard work, and while your definition of done should organically grow, you need to create the seed that you can build on.

I recommend that you run a workshop with the entire Scrum Team  , and likely some other domain experts. If there are Stage Gates that your software has to pass after Developers  are Done, then you need representatives from those Gates to participate in the workshop. Regardless of your product you likely need representatives with the following expertise; Code, Test, Security, UX, UI, Architecture, etc. You may have this expertise on your team, or you may need to bring in an expert from your organisation, or even external to your organisation.

Some examples of things to put on your definition of done:

Whatever Definition of Done  you come up with it is unlikely that your entire Product currently meets the criteria. You are not yet doing Scrum. Before you start Sprinting, you need to focus on making sure that your current Increment meets your new Definition of Done. Focus on Quality, which is what the Developers  are accountable for, and make sure that your Increment  meets that new quality bar before you start. The next Increment can only reach the quality bar of all those that came before do, but you can and should add to that quality bar  .

The Definition of Done  is the commitment to quality for the Increment  !

Create a usable increment that meets your definition of done and then start sprinting. Keeping your software in a working state will require a modern source control system that provides you with the facility to implement good DevOps  practices.

Growing your Definition of Done (DoD)

It’s super important that quality is always increasing, and that means that you will need to at least reflect on your Definition of Done on a regular cadence. In Scrum , this cadence is defined by your Sprint length, and you have a Kaizen moment at the Sprint Retrospective . That does not mean that you don’t reflect on your DOD all the time, you do. You reflect continuously on whether your increment currently meets your DoD, and what you need to do to get it there. You should always be reflecting on whether your DoD fits your needs. If your Developers finds that something is missing from the DoD halfway through the Sprint, then they should go ahead and add it, making sure that they are not endangering the Sprint Goal .

You may discover that you have a performance problem with your product as David Corbin pointed out in my previous post. How do we make sure that we fix that issue? As I see it there are two pieces to this once you are in flight. You can Scrumble (stop Sprinting because of poor quality), and fix it, or you can integrate this new knowledge into your product cycle.

If it is a significant issue that results in you not having working software, then you need to stop and fix. In Scrum, this is called a Scrumble, as a reflection that the Developers stumbled because something is missing. You should stop adding new features and create a usable increment before you continue Sprinting and adding new features. Once you have repaired the issue, you can increase your Definition of Done to make sure that all future Increments meet the new requirements.

If it is less significant, you might want to keep working and add what you need to your Product Backlog . You can then deliver improvements over the next few Sprints that mitigate and then resolve the identified issue. Once you have resolved it, you can then pin the outcome by adding something to your DoD.

Always look for ways that you can increase your quality. What does your definition of done look like today?

agility devops blog agile definition-of-done engineering-excellence homepage scrum scrumble

Connect with Martin Hinshelwood

If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.

Our Happy Clients​

We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.​

Illumina Logo
DFDS Logo
Kongsberg Maritime Logo
Genus Breeding Ltd Logo
Cognizant Microsoft Business Group (MBG) Logo
Trayport Logo
YearUp.org Logo
Bistech Logo
Deliotte Logo
MacDonald Humfrey (Automation) Ltd. Logo
Qualco Logo
ALS Life Sciences Logo
Alignment Healthcare Logo
Jack Links Logo

CR2

Xceptor - Process and Data Automation Logo
Sage Logo
Slicedbread Logo
Washington Department of Enterprise Services Logo
Department of Work and Pensions (UK) Logo
Washington Department of Transport Logo
New Hampshire Supreme Court Logo
Ghana Police Service Logo
Royal Air Force Logo
DFDS Logo
Illumina Logo
Epic Games Logo
Genus Breeding Ltd Logo
Slaughter and May Logo
Flowmaster (a Mentor Graphics Company) Logo