{"id":22930,"date":"2023-02-25T12:39:53","date_gmt":"2023-02-25T11:39:53","guid":{"rendered":"https:\/\/scrum-master.org\/definition-of-done-dod-everything-you-need-to-know\/"},"modified":"2024-06-20T20:55:32","modified_gmt":"2024-06-20T18:55:32","slug":"definition-of-done-dod-everything-you-need-to-know","status":"publish","type":"post","link":"https:\/\/scrum-master.org\/en\/definition-of-done-dod-everything-you-need-to-know\/","title":{"rendered":"Definition of Done (DoD): Everything you need to know"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"22930\" class=\"elementor elementor-22930 elementor-4405\" data-elementor-post-type=\"post\">\n\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-005d84d elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"005d84d\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-e481a38\" data-id=\"e481a38\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-32af085 elementor-widget elementor-widget-text-editor\" data-id=\"32af085\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The <strong>Definition of Done (DoD)<\/strong> stands as a fundamental principle within the <strong>Agile<\/strong> and <strong>Scrum<\/strong> methodologies, guiding development teams toward a clear understanding of what it means for a task, user story, or product increment to be considered &#8220;complete.&#8221; This clarity is crucial for ensuring that all <strong>product backlog<\/strong> items meet both stakeholder requirements and the team&#8217;s quality benchmarks.<\/p>\n<p>In this exploration of DoD, we delve into its significance for <strong>Scrum teams<\/strong>, illustrating how it fosters a shared understanding among team members, including the Product Owner, Scrum Master, and developers. We will also cover practical steps for crafting a DoD, the collaborative role each Scrum team member plays in this process, and strategies for effectively implementing DoD to achieve project success.<\/p>\n<p>Whether you&#8217;re new to <strong>Scrum<\/strong> or seeking to enhance your Agile team&#8217;s efficiency and output quality, this article offers valuable insights into DoD and its key role in software development.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-fc395d2 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"fc395d2\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-ab5e384\" data-id=\"ab5e384\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-9ea1576 elementor-widget elementor-widget-heading\" data-id=\"9ea1576\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">What is the Definition of Done (DoD)?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-6f3d403 elementor-widget elementor-widget-text-editor\" data-id=\"6f3d403\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>At its core, the <strong>Definition of Done<\/strong> establishes a comprehensive <strong>checklist<\/strong> of standards and criteria that <strong>S<\/strong>crum team members must adhere to for work to be considered complete. This checklist, essential for maintaining high-quality standards, is visible on management tools like <a href=\"https:\/\/scrum-master.org\/jira-tutoriel-francais-action-de-base\/\" target=\"_new\">Jira<\/a>, assisting teams in tracking and ensuring that each <strong>product backlog item<\/strong> crosses the finish line with all <strong>stakeholder<\/strong> expectations met.<\/p><p>The creation of the <strong>DoD<\/strong> is a collective endeavor, requiring input from all corners of the <strong>Scrum team<\/strong>. This collaborative process ensures that the <strong>DoD<\/strong> is tailored to the specific needs of the project, detailed enough to eliminate ambiguity, and flexible enough to cover a wide array of requirements, from <strong>acceptance criteria<\/strong> to <strong>increment<\/strong> validations like automated and manual testing, documentation, user acceptance, and sometimes, integration and security specifications.<\/p><p>By delineating what &#8220;finished&#8221; truly means, the <strong>DoD<\/strong> enables <strong>Scrum teams<\/strong> to uphold exceptional quality standards, ensuring that every <a href=\"https:\/\/scrum-master.org\/en\/what-is-a-product-backlog-understanding-your-role-in-product-management\/\"><strong>product backlog<\/strong><\/a> item not only fulfills <strong>stakeholder expectations<\/strong> but is also free from regressions or bugs, thanks to thorough testing before being deemed complete. In essence, the <strong>DoD<\/strong> is a critical component of the <strong>Agile Scrum methodology<\/strong>, instrumental in both preserving work quality and satisfying <strong>stakeholder<\/strong> demands. Its meticulous formulation is key to its effectiveness and utility for the team.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-9a26e7f elementor-widget elementor-widget-image\" data-id=\"9a26e7f\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<img fetchpriority=\"high\" decoding=\"async\" width=\"618\" height=\"378\" src=\"https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-illustration.png\" class=\"attachment-large size-large wp-image-22643\" alt=\"definition of done DoD for an agile Scrum team and list of acceptance criteria\" srcset=\"https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-illustration.png 618w, https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-illustration-300x183.png 300w, https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-illustration-150x92.png 150w\" sizes=\"(max-width: 618px) 100vw, 618px\" title=\"\">\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-dee90da elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"dee90da\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-7ce2a8a\" data-id=\"7ce2a8a\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-092616c elementor-widget elementor-widget-heading\" data-id=\"092616c\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">An example of Definition of Done<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7135e32 elementor-widget elementor-widget-text-editor\" data-id=\"7135e32\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>To illustrate the practical application of <strong>DoD<\/strong>, let&#8217;s consider an example for a team developing a classic website. A well-crafted <strong>Definition of Done<\/strong> for such a project might include:<\/p><ul><li>All page elements are functional and responsive across devices.<\/li><li>Text content is proofread, corrected, and aligns with the content strategy.<\/li><li>Images are optimized for the web and adhere to the graphic charter.<\/li><li>Cross-browser compatibility is tested and assured.<\/li><li>Page loading times meet current speed optimization standards.<\/li><li>The codebase is clean, well-documented, and follows development best practices.<\/li><li>All unit and functional tests are successfully passed.<\/li><\/ul><p>This <strong>checklist<\/strong> represents a snapshot of the diverse elements that might be considered to ensure a deliverable is truly &#8220;done.&#8221; It&#8217;s crucial that these criteria are specific to the team&#8217;s technical and functional environment, allowing for a tailored approach that best suits project needs.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-1564c67 elementor-widget elementor-widget-image\" data-id=\"1564c67\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<img decoding=\"async\" width=\"432\" height=\"219\" src=\"https:\/\/scrum-master.org\/wp-content\/uploads\/2021\/07\/image-5.png\" class=\"attachment-large size-large wp-image-22547\" alt=\"\" srcset=\"https:\/\/scrum-master.org\/wp-content\/uploads\/2021\/07\/image-5.png 432w, https:\/\/scrum-master.org\/wp-content\/uploads\/2021\/07\/image-5-300x152.png 300w, https:\/\/scrum-master.org\/wp-content\/uploads\/2021\/07\/image-5-150x76.png 150w\" sizes=\"(max-width: 432px) 100vw, 432px\" title=\"\">\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-ba49f22 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"ba49f22\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-c8af0fd\" data-id=\"c8af0fd\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-34e5188 elementor-widget elementor-widget-heading\" data-id=\"34e5188\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Role of Scrum Team Members in Implementing DoD<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-e3f5543 elementor-widget elementor-widget-text-editor\" data-id=\"e3f5543\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The effective implementation of the <strong>Definition of Done<\/strong> is a collaborative effort, involving key roles within the <strong>Scrum team<\/strong>:<\/p><ul><li><p><strong>The <a href=\"https:\/\/scrum-master.org\/en\/scrum-master-role-definition-responsibilities-skills-and-salary\/\" target=\"_new\">Scrum Master<\/a><\/strong> champions the <strong>DoD<\/strong> process, ensuring all team members understand and adhere to its criteria. This role involves facilitating discussions around the <strong>DoD<\/strong>, helping the team to update it as necessary to reflect evolving project needs or challenges.<\/p><\/li><li><p><strong>The <a href=\"https:\/\/scrum-master.org\/en\/product-owner-understanding-your-role-and-responsibilities-in-the-agile-framework\/\" target=\"_new\">Product Owner<\/a><\/strong> works closely with the <strong>development team<\/strong> to define the <strong>DoD<\/strong> requirements. This ensures that the <strong>DoD<\/strong> aligns with both company objectives and user needs, making it a vital tool for delivering value. The <strong>Product Owner<\/strong> also plays a critical role in clarifying any ambiguities in the <strong>DoD<\/strong> to ensure it&#8217;s comprehensible and actionable for the team.<\/p><\/li><li><p><strong>Development team members<\/strong> are tasked with the hands-on application of the <strong>DoD<\/strong> criteria to their work on <strong>sprint<\/strong> tasks. This group must ensure that each <strong>product backlog item<\/strong> not only meets the defined <strong>DoD<\/strong> standards before being considered complete but also engages in continuous dialogue with the <strong>Product Owner<\/strong> and <strong>Scrum Master<\/strong> to verify that the <strong>DoD<\/strong> remains relevant and comprehensive.<\/p><\/li><\/ul><p>In summary, the <strong>DoD<\/strong> is a collective responsibility that requires clear communication and shared understanding among the <strong>Product Owner<\/strong>, <strong>Scrum Master<\/strong>, and <strong>development team<\/strong>. Its clarity, comprehensibility, and alignment with organizational goals are fundamental to its success and effectiveness.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-622bf942 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"622bf942\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-68263524\" data-id=\"68263524\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-3e34eb1 elementor-widget elementor-widget-spacer\" data-id=\"3e34eb1\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"spacer.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"elementor-spacer\">\n\t\t\t<div class=\"elementor-spacer-inner\"><\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-22d2d83 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"22d2d83\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-89e38ae\" data-id=\"89e38ae\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-553e13f elementor-widget elementor-widget-heading\" data-id=\"553e13f\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Implementing DoD for the First Time in an Agile Team<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-f6613a5 elementor-widget__width-initial elementor-widget elementor-widget-text-editor\" data-id=\"f6613a5\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Initiating the <strong>Definition of Done (DoD)<\/strong> within a team, especially one new to <strong>Agile<\/strong> practices, requires a structured approach. Here are steps to facilitate a successful <strong>DoD<\/strong> workshop:<\/p><ol><li><p><strong>Introduce the Concept<\/strong>: Begin by explaining the <strong>DoD<\/strong>, its purpose, and its importance in ensuring <strong>product quality<\/strong> and meeting <strong>stakeholder expectations<\/strong>. Utilizing examples can help illustrate its impact on project success.<\/p><\/li><li><p><strong>Identify Quality Criteria<\/strong>: Engage the team in identifying all relevant quality criteria for your project, such as performance, security, and browser compatibility. This brainstorming session ensures a comprehensive list that reflects the project&#8217;s needs.<\/p><\/li><li><p><strong>Prioritize the Criteria<\/strong>: Collaboratively prioritize these criteria based on their significance to the project&#8217;s success. This step helps focus efforts on aspects that offer the most value.<\/p><\/li><li><p><strong>Draft the DoD<\/strong>: Use the prioritized list to create a detailed <strong>DoD<\/strong> that encompasses all agreed-upon quality standards. This checklist will serve as the team&#8217;s guide to determining when a task is truly complete.<\/p><\/li><li><p><strong>Validate the DoD<\/strong>: Seek team consensus on the draft <strong>DoD<\/strong>. It&#8217;s essential for every <strong>team member<\/strong> to understand and agree on what each criterion entails and how it applies to their work.<\/p><\/li><li><p><strong>Monitor and Adapt the DoD<\/strong>: Regularly review the <strong>DoD<\/strong> to ensure it remains relevant and effective. Be prepared to adapt it in response to new insights, project evolution, or feedback from <strong>sprint reviews<\/strong>.<\/p><\/li><\/ol><p>To enhance the interactive experience of defining your team&#8217;s <strong>Definition of Done<\/strong>, consider organizing a <strong>DoD Kards<\/strong> workshop. Based on my experience with this engaging format in previous missions, it not only fosters collaboration but also adds an element of fun to the process. For a seamless start, access and download the <strong>DoD Kards<\/strong> in both English and PDF format directly from <a href=\"https:\/\/pxl.to\/tivnmu5\" target=\"_new\" rel=\"noopener\">Coach-Agile.com Drive<\/a>. This tool is an excellent resource for bringing clarity and shared understanding to your <strong>Agile team&#8217;s<\/strong> DoD discussions<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-d7af438 elementor-widget elementor-widget-image\" data-id=\"d7af438\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"image.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<img decoding=\"async\" width=\"1024\" height=\"602\" src=\"https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-kards-atelier-1024x602.png\" class=\"attachment-large size-large wp-image-22644\" alt=\"\" srcset=\"https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-kards-atelier-1024x602.png 1024w, https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-kards-atelier-300x176.png 300w, https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-kards-atelier-768x451.png 768w, https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-kards-atelier-150x88.png 150w, https:\/\/scrum-master.org\/wp-content\/uploads\/2023\/02\/dod-definition-of-done-kards-atelier.png 1087w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" title=\"\">\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-beaf27d elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"beaf27d\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-9cb7810\" data-id=\"9cb7810\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-89ac675 elementor-widget elementor-widget-heading\" data-id=\"89ac675\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">What's the difference between acceptance criteria and DoD?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-07f2ae2 elementor-widget elementor-widget-text-editor\" data-id=\"07f2ae2\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>While both <strong>acceptance criteria<\/strong> and the <strong>Definition of Done<\/strong> play crucial roles in <strong>Agile<\/strong> and <strong>Scrum<\/strong> methodologies, it&#8217;s important to understand their differences:<\/p><ul><li><p><strong>Acceptance Criteria<\/strong> are specific to each <strong>product backlog item<\/strong>, detailing the conditions that must be met for the work to satisfy customer needs and receive approval. These criteria are agreed upon before <a href=\"https:\/\/scrum-master.org\/en\/scrum-ceremony-guide-your-path-to-a-successful-sprint\/\" target=\"_blank\" rel=\"noopener\"><strong>sprint planning<\/strong><\/a> and are essential for guiding development with clear, measurable goals.<\/p><\/li><li><p>The <strong>DoD<\/strong>, on the other hand, represents a broader set of quality standards and practices that apply universally to all tasks undertaken by the <strong>development team<\/strong>. Unlike acceptance criteria, which vary from item to item, the <strong>DoD<\/strong> is consistent across the board, ensuring a uniform quality level and completeness for all deliverables.<\/p><\/li><\/ul><p>Understanding and effectively implementing both concepts are vital for <strong>Scrum teams<\/strong> to deliver high-quality products that meet both the <a href=\"https:\/\/scrum-master.org\/en\/definition-of-ready-dor-an-essential-tool-for-improving-software-development-quality\/\" target=\"_blank\" rel=\"noopener\"><strong>Definition of Ready<\/strong><\/a> and the stakeholders&#8217; expectations. The <strong>DoD<\/strong> and acceptance criteria complement each other, providing a dual framework that guides the <strong>Scrum team<\/strong> towards excellence in <strong>product development<\/strong>.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-b340d75 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"b340d75\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-05de417\" data-id=\"05de417\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-be18368 elementor-widget elementor-widget-heading\" data-id=\"be18368\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Wrapping Up<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-cb6b33a elementor-widget elementor-widget-text-editor\" data-id=\"cb6b33a\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>In summary, the Definition of Done (DoD) is an indispensable aspect of the Scrum methodology, playing a pivotal role in ensuring the quality and value of deliverables. It equips the development team with a clear set of criteria for what constitutes &#8220;done,&#8221; guaranteeing that every product backlog item aligns with stakeholder expectations and adheres to predefined quality and acceptance standards.<\/p><p>The establishment of these criteria, ideally before sprint planning begins, significantly boosts the team&#8217;s efficiency and productivity. It streamlines the software development process, mitigating potential risks and preempting issues that could arise later. Thus, the DoD is fundamental in fulfilling Scrum&#8217;s mission: the swift delivery of a superior product that not only meets but exceeds the customer&#8217;s expectations. Through fostering a shared understanding among Scrum team members, including the Product Owner and Scrum Master, the DoD helps navigate the complexities of product development, ensuring a successful, transparent, and cohesive approach to Agile project management.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t<div class=\"elementor-element elementor-element-91a1d2c e-flex e-con-boxed e-con e-parent\" data-id=\"91a1d2c\" data-element_type=\"container\" data-e-type=\"container\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-8bc7017 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"8bc7017\" data-element_type=\"section\" data-e-type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-29ea641\" data-id=\"29ea641\" data-element_type=\"column\" data-e-type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t<div class=\"elementor-element elementor-element-aaec2e2 elementor-widget elementor-widget-heading\" data-id=\"aaec2e2\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Further information<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-6edc7e4 elementor-widget elementor-widget-text-editor\" data-id=\"6edc7e4\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>For those keen to explore more about the Definition of Done and delve deeper into Agile and Scrum practices, numerous resources are available to enrich your understanding:<\/p><ul><li><p><a href=\"https:\/\/amzn.to\/3ISnWlv\" target=\"_new\" rel=\"noopener\">&#8220;Scrum &#8211; The Art of Doing Twice the Work in Half the Time&#8221;<\/a> by Jeff Sutherland offers insightful perspectives on maximizing productivity within Scrum teams.<\/p><\/li><li><p><a href=\"https:\/\/amzn.to\/3StZpqc\" target=\"_new\" rel=\"noopener\">&#8220;Succeeding with Agile: Software Development Using Scrum&#8221;<\/a> by Mike Cohn provides a comprehensive guide to effective Agile software development, highlighting strategies for success.<\/p><\/li><li><p><a href=\"https:\/\/amzn.to\/3EEsedI\" target=\"_new\" rel=\"noopener\">&#8220;The Lean Startup: How Today&#8217;s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses&#8221;<\/a> by Eric Ries explores the principles of lean thinking in startup environments, applicable in Agile methodologies.<\/p><\/li><li><p>For a foundational understanding of prerequisites before sprint commencements, our article on <a href=\"https:\/\/scrum-master.org\/en\/definition-of-ready-dor-an-essential-tool-for-improving-software-development-quality\/\" target=\"_new\">the Definition of Ready<\/a> complements the knowledge of DoD.<\/p><\/li><\/ul><p>These resources serve as a springboard for further learning and application of Agile and Scrum methodologies, empowering you to elevate your software development practices.<\/p><p>We hope this guide has illuminated the path to understanding and implementing the Definition of Done, emphasizing its critical role in the Scrum framework.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>The Definition of Done (DoD) stands as a fundamental principle within the Agile and Scrum methodologies, guiding development teams toward a clear understanding of what it means for a task, user story, or product increment to be considered &#8220;complete.&#8221; This clarity is crucial for ensuring that all product backlog items meet both stakeholder requirements and [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":22644,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[139,143],"tags":[],"class_list":["post-22930","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-scrum-en","category-safe-en"],"_links":{"self":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts\/22930","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/comments?post=22930"}],"version-history":[{"count":0,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/posts\/22930\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/media\/22644"}],"wp:attachment":[{"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/media?parent=22930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/categories?post=22930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/scrum-master.org\/en\/wp-json\/wp\/v2\/tags?post=22930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}