{"id":6622,"date":"2024-06-17T17:33:33","date_gmt":"2024-06-17T16:33:33","guid":{"rendered":"https:\/\/thescrumacademy.com\/?p=6622"},"modified":"2024-07-09T18:32:24","modified_gmt":"2024-07-09T17:32:24","slug":"definition-of-done-define-it-or-doom-your-sprints","status":"publish","type":"post","link":"https:\/\/thescrumacademy.com\/es\/2024\/06\/17\/definition-of-done-define-it-or-doom-your-sprints\/","title":{"rendered":"Definition of Done: Define It or Doom Your Sprints"},"content":{"rendered":"

A Definition of Done (DoD) is non-negotiable if you want to #DoBetterScrum.\u00a0 The best Scrum Teams co-create their DoD with their Product Owner, Scrum Master Developers and stakeholders.\u00a0 To learn more about what steps you need to take in order to build a strong DoD, read on.<\/span><\/p>\n

When to create a Definition of Done<\/span><\/h2>\n

If your team is new to Scrum, one of the first tasks you need to complete is to create a DoD prior to your first Sprint Planning meeting.\u00a0 IME, without a clear understanding of how your team <\/span>defines quality<\/span><\/a>, you cannot have an effective Sprint Planning meeting.<\/span><\/p>\n

For existing Scrum Teams that lack a DoD, the <\/span>next Retrospective<\/span><\/a> is an ideal time to create (or refine) it.\u00a0 Please keep in mind, the lack of a DoD is a high priority issue that both the Scrum Master and Product Owner need to address.\u00a0 There are no benefits associated with delaying this conversation.<\/span><\/p>\n

Who creates the Definition of Done<\/span><\/h2>\n

The obvious participants are the Developers, Product Owner and Scrum Master.\u00a0 I also recommend including the key stakeholders in this discussion.\u00a0 There are two reasons for this.\u00a0 One, stakeholder participation gives them insights into the full scope of what is required in order to deliver the product or service.\u00a0 Two, when discussing impediments to getting to done, it is often stakeholders who have the authority to eliminate these impediments.\u00a0 By having them present in this discussion, decisions on how to resolve these impediments can be made on the spot.\u00a0\u00a0<\/span><\/p>\n

Four steps to creating a Definition of Done<\/span><\/h2>\n

\u00a0 \u00a0 \u00a01. \u00a0Identify Activities: <\/b>give everyone on the Scrum Team, and their key stakeholders, some post-it notes and a marker (or their digital equivalents).\u00a0 Next, ask them to write down every task that is required to take a Product Backlog item from conception to delivery; be sure to include any documentation that may be required.\u00a0 Set the expectation that each person should strive to identify from ten to fifteen items.\u00a0<\/span><\/p>\n

\"\"<\/a><\/span><\/p>\n

\u00a0 \u00a0 \u00a02. \u00a0Review & Organize: <\/b>at this point, you will have a large collection of notes that roughly outlines the <\/span>value stream<\/span><\/a> of the Scrum Team.\u00a0 Next, post a large sheet of chart paper on the wall (or the digital equivalent) and draw a blue line across the middle.\u00a0 Start your review by removing the duplicates.\u00a0 With the remaining items, select a post-it note and ask the Developers, \u201cWill you complete this activity for each Product Backlog item in every Sprint?\u201d.\u00a0\u00a0<\/span><\/p>\n