how_do_we_initially_setup_our_definition_of_done
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| how_do_we_initially_setup_our_definition_of_done [2020/04/13 10:40] – [How Do We Ensure Done is Actually Done?] Changed to reflect more modern testing approach hpsamios | how_do_we_initially_setup_our_definition_of_done [2020/04/13 10:53] – Added example hpsamios | ||
|---|---|---|---|
| Line 34: | Line 34: | ||
| Once complete, this is your Definition of Done. Document it and make sure its part of every planning session you have. | Once complete, this is your Definition of Done. Document it and make sure its part of every planning session you have. | ||
| + | |||
| + | ====== Sample Definition of Done ====== | ||
| + | |||
| + | There is no such thing as one Definition of Done that applies everywhere. Your environment, | ||
| + | |||
| + | * Code produced (all ‘to do’ items in code completed) | ||
| + | * Code commented, checked in and run against trunk in source control | ||
| + | * Peer reviewed (or produced with pair programming) and meeting development standards | ||
| + | * Builds without errors | ||
| + | * Unit tests written and passing | ||
| + | * Deployed to system test environment and passed system tests | ||
| + | * Passed UAT (User Acceptance Testing) and signed off by Product Owner as meeting requirements | ||
| + | * Any build, deployment, or configuration changes are implemented, | ||
| + | * Relevant documentation/ | ||
| + | * Remaining hours for task set to zero and task closed | ||
| + | * No known remaining work because we simply did not track it | ||
| + | * For each user story no additional bugs added to list of defects | ||
| + | * Code checked-out of source control is checked-in in better shape | ||
| ====== How Do We Ensure Done is Actually Done? ====== | ====== How Do We Ensure Done is Actually Done? ====== | ||
| Line 47: | Line 65: | ||
| Sometimes you will encounter the situation where you would like to improve the Definition of Done, but as yet you cannot as you don't have the capability. For example, perhaps your Team has never done automated testing before and now would like to do it. In this case your could create a Feature or Story that defined the work to figure our how to do work (automated testing in this case), and the acceptance criteria might include something like "Must become part of our Definition of Done". | Sometimes you will encounter the situation where you would like to improve the Definition of Done, but as yet you cannot as you don't have the capability. For example, perhaps your Team has never done automated testing before and now would like to do it. In this case your could create a Feature or Story that defined the work to figure our how to do work (automated testing in this case), and the acceptance criteria might include something like "Must become part of our Definition of Done". | ||
| - | {{tag> | + | {{tag> |
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/how_do_we_initially_setup_our_definition_of_done.txt · Last modified: 2021/04/28 12:47 by hans