| Table of Contents |
|---|
The definition of Done (DoD) represents the checklist that CPS agile team must meet before it can consider closing relevant work items such as (stories, bugs and epic).
User Story
DoD for User Story | |
|---|---|
| 1 | Code reviewed and Merged shall follow the code review process as listed in CPS Ways of Working (WoW) |
| 2 | Latest Yaml files copied to /docs folder (see step2 on CPS Release Process) |
| 3 | Consider necessary documentation |
| 4 | Release Notes updated
|
| 5 | Consider new functionality Demoed to Team and Stakeholders
|
| 6 | Update Jira with comments even if it's just a 1 liner of code that was input for the story |
| 7 | All Acceptance Criteria of the User Story have been met |
...
DoD for Epic | |
|---|---|
| 1 | Consider End2End Demo for the epic |
| 2 | Doublecheck necessary documentation and release note |
| 3 | End2End integration/acceptance testing must have been done and completed according to CPS Ways of Working (WoW) |
| 4 | Agree delivery of overall epic with stakeholders in planning meeting |
| 5 | PO to state overall/summary of the value each feature added during epic completion. Create a link for PO and PTL use in release note updates for external stakeholders |
Recommend having DoD handy - possibly print it out or have a sticker on your working desk
| Expand | ||
|---|---|---|
| ||
Fault Slip Through Analysis
|
...