https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/ Recent content in Definition of Done on Engineering Leadership in AI & Software Hugo en Tue, 16 Jun 2026 17:40:35 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ Wed, 14 May 2025 07:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-a-shared-definition-of-done-is-the-secret-to-consistent-predictable-quality-in-agile-teams/ When teams lack a shared definition of done, quality and predictability suffer, leading to confusion, hidden risks, and technical debt. Aligning on a clear, organisation-wide standard ensures consistent delivery, builds trust, and reduces production risks. Development managers should prioritise creating and enforcing a common definition of done to achieve reliable outcomes and true agility. https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ Mon, 28 Jul 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-is-a-commitment-to-quality/ A clear, shared Definition of Done is essential for delivering quality, releasable software in Scrum and aligns teams on what “complete” means. It ensures transparency, predictability, and accountability, protects your product’s reputation, and must be created, automated, and regularly improved by all teams working on a product. Development managers should prioritise running DoD workshops, making standards visible, automating checks, and reviewing the DoD every sprint to maintain quality and reduce risk. https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/ Mon, 31 Mar 2025 09:00:00 +0100 https://engineering-leadership-preview.hinshelwood.com/articles/your-evolving-definition-of-done/ The Definition of Done should evolve as teams mature, starting with basic quality standards and expanding to include automation, security, and business-level requirements that align with organisational goals. A strong, consistently applied DoD reduces risk, rework, and delays, ensuring every increment is truly releasable and delivers real value. Development managers should regularly review and raise the DoD, embedding it into team practices to protect quality and support strategic objectives. https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Wed, 21 May 2025 06:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-paying-the-hidden-costs-of-weak-delivery-why-a-strong-definition-of-done-transforms-your-team-s-results/ Cutting corners on quality and having a weak definition of done leads to hidden costs like rework, production risks, and lost trust. A clear, shared, and enforceable definition of done ensures every increment is truly usable, reliable, and aligned with business goals. Make your definition of done visible, evidence-based, and strictly enforced to improve delivery outcomes and build stakeholder confidence. https://engineering-leadership-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/ Thu, 03 Apr 2025 15:30:01 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/scrum-teams-don-t-set-the-bar-for-quality-they-meet-it/ Scrum teams are responsible for meeting, not setting, the quality standard defined by the Definition of Done, which should be a strict, non-negotiable measure of what is releasable. Weakening or fluctuating the DoD increases risk and technical debt, undermining quality and predictability. Development managers should ensure their teams consistently strengthen the DoD over time rather than lowering it to deliver more features. https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ Fri, 03 Jan 2025 00:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/definition-of-done-objective-vs-subjective/ The Definition of Done (DoD) in Scrum is an objective, measurable checklist that sets the minimum quality standard for every product increment, distinct from the more subjective Product and Sprint Goals. Teams should ensure their DoD is clear, comprehensive, regularly reviewed, and as automated as possible, avoiding subjective approval steps. Development managers should treat the DoD as a non-negotiable baseline for quality, not a ceiling, and keep it updated to reflect evolving standards and business needs. https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Wed, 16 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-your-team-needs-to-win/ Many teams struggle not with building software but with finishing it in a way that delivers real business value. A clear, evolving definition of done protects revenue, boosts customer satisfaction, reduces rework, and builds trust by ensuring work is truly complete and valuable. Make your definition of done visible, review it regularly with the whole team, and connect it to real outcomes to turn it into a competitive advantage. https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Wed, 02 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/acceptance-criteria-vs-definition-of-done-why-getting-this-right-builds-trust-and-delivers-quality-faster/ Acceptance criteria specify what each backlog item must do, while the definition of done sets the minimum quality standards for all work. Confusing the two leads to missed requirements, technical debt, and loss of trust. Make both explicit and review them regularly to ensure faster delivery and consistent quality. https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/ Wed, 18 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-the-secret-weapon-for-real-business-impact-and-agile-growth/ A strong definition of done is crucial for delivering real business value, not just completing tasks. When done means features are live, usable, and measured for impact, teams deliver value faster, reduce risk, and become more adaptable. Make your definition of done visible, connect it to measurable outcomes, and continuously refine it to drive growth and true agility. https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Thu, 27 Jun 2024 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-power-of-technical-excellence-in-agile-development/ Technical excellence is essential for delivering a usable, high-quality product at the end of every iteration, which reduces risk and enables faster, more valuable feature delivery. The Azure DevOps team at Microsoft dramatically increased their output by focusing on paying down technical debt and establishing a strong Definition of Done. Development managers should prioritize technical excellence, avoid sacrificing quality for speed, and ensure their teams have a clear Definition of Done to maximize value and stay competitive. https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Wed, 09 Jul 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-your-definition-of-done-is-holding-back-quality-agility-and-trust-and-how-to-raise-the-bar/ Treating “done” as a vague checklist limits quality, agility, and stakeholder trust; instead, teams should define “done” as delivering thoroughly tested, production-ready, and valuable increments that work in the real world. Clear, objective standards for “done” reduce defects, speed up learning, and build confidence with stakeholders. Development managers should work with their teams to set and uphold a robust definition of “done” to drive better outcomes and long-term success. https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ Wed, 25 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/how-to-evolve-your-definition-of-done-start-small-grow-smarter-and-build-lasting-momentum/ You do not need a perfect Definition of Done from the start; begin with what is usable, then gradually add quality, testing, and compliance standards as your team grows more capable. Trying to do everything at once can stall progress, so evolve your standards step by step to build momentum and resilience. Focus on essential requirements now and raise the bar as your team is ready. https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Wed, 11 Jun 2025 06:45:00 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/stop-flying-blind-why-telemetry-belongs-in-your-definition-of-done/ Shipping software without telemetry leaves teams guessing about usage, performance, and user behavior, which prevents learning and improvement. Teams that make telemetry a core part of their Definition of Done catch issues early, validate outcomes with real data, and make better decisions. To deliver real value, define telemetry needs upfront, automate data collection, review feedback regularly, and act on what you learn. https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ Mon, 14 Oct 2019 13:55:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/can-the-definition-of-done-change-per-sprint/ The Definition of Done can be improved each Sprint to raise quality but should never be changed to lower standards or to vary by backlog item, as this undermines transparency and product value. Consistency in the Definition of Done ensures everyone understands what a usable increment means and supports reliable delivery. Development managers should encourage teams to strengthen the Definition of Done over time, aiming for a shippable product each Sprint. https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/ Mon, 31 Mar 2025 15:30:08 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/executives-want-predictability/ If your teams do not have a clear, enforced Definition of Done, you are creating hidden risks and unreliable forecasts, which leads to missed deadlines and frustrated customers. Treating “Done” as negotiable means you are not delivering real value or predictability. Make sure your teams only mark work as done when it meets objective, enforceable standards to ensure true progress and trustworthy commitments. https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/ Thu, 07 Dec 2023 11:00:05 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/bridging-the-gap-understanding-the-true-meaning-of-done-in-agile-teams/ Many Agile teams misunderstand what “done” really means, leading to gaps in quality and unmet expectations. Clearly defining “done” with input from both leadership and the team ensures consistent quality, reduces rework, and builds trust with stakeholders. Development managers should regularly review and refine their team’s definition of done to align with evolving business needs and maintain high standards. https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Fri, 04 Apr 2025 15:30:02 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/a-changing-definition-of-done-undermines-quality-and-predictability-in-teams/ Frequently changing the Definition of Done makes it hard for teams to deliver predictable results and maintain quality. The Definition of Done should only evolve to raise standards, not lower them. To improve predictability and quality, keep your Definition of Done consistent and ensure it is followed. https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ Sat, 05 Apr 2025 15:30:00 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/if-every-release-feels-high-risk-you-lack-a-true-definition-of-done/ If every release feels risky and stressful, your team likely lacks a clear Definition of Done that ensures software is truly ready for production. A strong Definition of Done means releases are routine, with quality, security, and compliance built in, so there are no last-minute scrambles. Review your team’s process to make releases predictable and low-stress. https://engineering-leadership-preview.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/ Tue, 01 Apr 2025 15:30:02 +0100 https://engineering-leadership-preview.hinshelwood.com/signals/why-compromising-on-software-quality-is-a-leadership-decision/ Compromising on software quality is a leadership decision, not a team one, and lowering standards to meet deadlines carries business risks that should be explicitly approved by leadership. A clear Definition of Done helps maintain consistent quality, and any decision to reduce it should be transparent and deliberate. Development managers should ensure quality expectations are set and upheld at the leadership level, not left to teams under delivery pressure. https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ Mon, 14 Dec 2020 13:03:00 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/getting-started-with-a-definition-of-done-dod/ A clear Definition of Done (DoD) is essential for ensuring software quality and predictable delivery, as it sets shared criteria for what “done” means for every increment. Involve the whole Scrum Team and relevant experts to create a short, measurable checklist that covers code quality, testing, security, and usability, and review it regularly to keep raising the quality bar. Before starting sprints, make sure your current increment meets the DoD, and continuously improve both your software and your DoD to maintain a working, shippable product. https://engineering-leadership-preview.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/ Thu, 07 Dec 2023 07:00:02 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/the-overlooked-virtue-of-agility-diligence/ Diligence, or consistently following through on quality standards like the definition of done, is often overlooked in Agile teams but is essential for reliable delivery and long-term success. Without diligence, teams risk inconsistent quality and increased rework, while a strong focus on it leads to better products and faster delivery over time. Development managers should ensure the definition of done is clear, visible, and enforced, and foster a culture of accountability and perseverance to make diligence a team habit. https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/ Mon, 13 Nov 2023 06:56:47 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/unlocking-success-in-agile-why-your-definition-of-done-is-essential-for-quality-delivery/ A clear and shared Definition of Done is essential for delivering quality products in Agile and Scrum, as it sets the standard for what is considered complete and ensures transparency across the team. Without it, teams risk miscommunication, unfinished work, and features that do not meet user needs. Development managers should regularly review and reinforce the Definition of Done with their teams to improve quality and reduce risk. https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/ Wed, 27 Sep 2023 09:59:46 +0000 https://engineering-leadership-preview.hinshelwood.com/articles/the-definition-of-done-ensuring-quality-without-compromising-value/ The Definition of Done (DoD) ensures every release meets clear quality standards, while acceptance criteria define specific content requirements. Mixing acceptance criteria into the DoD can undermine transparency and adaptability, but consistently required quality measures should be added to the DoD itself. Review your acceptance criteria regularly and only update the DoD if it preserves both clarity and flexibility in your team’s delivery. https://engineering-leadership-preview.hinshelwood.com/videos/why-'definition-of-done'-is-crucial-for-success-in-scrum/ Tue, 14 Nov 2023 07:00:30 +0000 https://engineering-leadership-preview.hinshelwood.com/videos/why-'definition-of-done'-is-crucial-for-success-in-scrum/ The Definition of Done sets clear quality standards for all work, ensuring every deliverable meets your organization’s expectations regardless of the specific feature or project. It aligns teams, reduces defects, and protects your brand by making sure nothing is released before it is truly ready. Regularly review and adapt your Definition of Done with your team to maintain high quality and customer satisfaction. https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/ Mon, 05 May 2025 09:00:00 +0000 https://engineering-leadership-preview.hinshelwood.com/tags/definition-of-done/ The Definition of Done (DoD) is a critical framework that establishes a shared understanding of what constitutes a completed and releasable product increment within agile and DevOps environments. Originating from the need for clarity in product development, the DoD serves as an organisational standard that all teams must adhere to, ensuring that every increment meets minimum quality criteria before it can be considered complete. This framework is vital for fostering transparency and consistency across teams, enabling empirical decision-making based on real-world feedback. By defining specific criteria, such as deployment in production, telemetry collection, and validation of initial hypotheses, the DoD helps mitigate risks associated with incomplete or subpar work, thereby reducing technical debt and enhancing the overall quality of deliverables. Furthermore, it facilitates faster feedback loops and iterative learning, allowing teams to adapt their processes based on actual performance data. The DoD not only clarifies expectations for stakeholders but also protects the integrity of the product, ensuring that increments are valuable, verifiable, and ready for real-world use. In essence, the Definition of Done is foundational to maintaining high standards in product development, promoting alignment among teams, and ultimately driving successful outcomes in organisational design and delivery.