Scrum Teams don’t set the bar for quality—they meet it

TL;DR; Scrum teams are responsible for meeting, not setting, the quality standard defined by the Definition of Done, which should be a strict and evolving benchmark for what is releasable. Treating the DoD as negotiable increases risk and technical debt, undermining control over quality and revenue. Development managers should ensure their teams regularly strengthen the DoD to maintain high standards and reduce long-term risk.

Published on 6 April 2025

Written by Martin Hinshelwood

1 minute read

https://nkdagility.com/resources/5lIasyqT9Rm

Scrum Teams don’t set the bar for quality—they meet it. The Definition of Done (DoD) isn’t a wishlist or a stretch goal. It’s a hard line that determines what is releasable. And if your DoD isn’t improving Sprint over Sprint, you’re accumulating risk and technical debt.

Too many teams treat DoD as negotiable. It’s not. It’s governance. It ensures predictability, manages risk, and protects revenue. A weak or fluctuating DoD means your organisation has no real control over quality.

If someone suggests lowering the DoD to “deliver more features,” ask them to get it in writing from the financial director—because that’s not a technical decision, it’s a financial and risk decision.

Your Definition of Done should never be static, but always evolving to maximise the quality. Anything less is dysfunction.

How often is your team strengthening its DoD?

Also published on: LinkedIn

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.