Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • how_do_we_deal_with_constant_interruptions
what_does_it_mean_to_be_done

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
what_does_it_mean_to_be_done [2021/04/28 12:42] – hanswhat_does_it_mean_to_be_done [2021/04/28 12:45] (current) – [Who is Responsible for the Definition of Done?] hans
Line 51: Line 51:
 > "Make the change easy; then make the easy change." - Kent Beck > "Make the change easy; then make the easy change." - Kent Beck
  
-Or establish a working agreement whereby as you work an area of code and see something that need fixing you create a reference to the changes needed. Then the next time someone on the Team has to go into that code base, you ensure that the estimate that you provide to do the work also include the work required to fix the area.+Or establish a working agreement whereby as you work an area of code and see something that needs fixing, you create a reference and estimate the changes needed. Then, the next time someone on the Team has to go into that code base, you ensure that the estimate that you provide to do the new work also includes the work required to fix the existing problems.
  
 No matter what, do not underestimate the impact of incremental improvements - see [[how_do_small_changes_lead_to_big_improvements|How Do Small Changes Lead to Big Improvements?]] for more information. No matter what, do not underestimate the impact of incremental improvements - see [[how_do_small_changes_lead_to_big_improvements|How Do Small Changes Lead to Big Improvements?]] for more information.
Line 70: Line 70:
   - Agile Team: Things the team learns it needs, especially at a technical level   - Agile Team: Things the team learns it needs, especially at a technical level
  
-Teams have a known, public DoD. Teams are explicit both in being visible about their DoD (available on the Scrum Team's page). They are also transparent about the practice they use to ensure their Definition of Done is addressed. It is up to the team to determine their approach.+Teams have a known, public DoD. Teams are explicit both in being visible about their DoD (for example, available on the Team's page). They are also transparent about the practice they use to ensure their Definition of Done is addressed. It is up to the team to determine their approach.
  
 Example approaches we have seen include: Example approaches we have seen include:
  
-  * Teams create tasks associated with their definition of done so that when the sub-tasks are done, the story is done.+  * Teams create tasks associated with their DoD so that when the sub-tasks are done, the story is done.
   * Teams maintain a spreadsheet and check-off the definition of done at the end of the Sprint.   * Teams maintain a spreadsheet and check-off the definition of done at the end of the Sprint.
   * Teams create a task that is the Definition of Done checklist that is updated as work proceeds on the story   * Teams create a task that is the Definition of Done checklist that is updated as work proceeds on the story
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/what_does_it_mean_to_be_done.1619638947.txt.gz · Last modified: 2021/04/28 12:42 by hans