Agile fundamentals for teams

In this video, we’re going to look at creating a definition of done. We'll explore what it is and the benefits of creating one. 

A Definition of Done is a set of items, agreed with the team, which they must complete. Like acceptance criteria, this serves as a checklist. Something is only considered done, once you have completed all items. 

The Definition of Done applies to all items in the product backlog. This differentiates it from acceptance criteria, which is unique to each item. 

Let's look at an example. Imagine a team is developing a website. They could use this as their Definition of Done: 

Any content will have to be trio-written. This means they developed bilingual content alongside content designers and translators. This ensures it makes sense in both Welsh and English. 

Next, they must ensure it meets the appropriate branding guidelines. 

For the content to be accessible, it must meet Web Content Accessibility Guidelines. 

Finally, it will have to go through testing. They will need to resolve any problems they find. 

This applies to all items in the backlog. Whether they're creating a button or a blog post, the same definition of done applies. 

A definition of done defines the quality standard that the team must meet. It prevents teams releasing something that doesn't meet the expected standard. 

Doing so reduces risk. This is critical when considering our duty around Welsh language and accessibility requirements. 

Finally, it ensures there’s alignment and clarity amongst the team. This is because everyone is aware of and working towards the same standard.