Understanding The DOD
The Definition of Done (DoD) is when all conditions, or acceptance criteria, that a software product must satisfy are ready to obtain by a user, customer, team, or consuming system. We must meet the DOD to ensure quality. It lowers rework, by preventing user stories that don’t meet the definition from being promoted to higher-level environments. It will prevent features that don’t meet the definition from being delivered to the customer or user.
USER STORIES
The most common use of DoD is on the delivery team level. Done on this level means the Product Owner reviewed and accepted the user story. Once accepted, the “done” user story will contribute to the team velocity. You must meet all of the defined criteria to complete the user story.
User Story DoD Examples:
- Firstly, Unit tests passed
- Secondly, Code reviewed
- Acceptance criteria met
- Functional tests passed
- Non-Functional requirements met
- Lastly, the Product Owner accepts the User Story
Expected Benefits: Definition Of Done
- Firstly, the DOD provides a checklist which usefully guides pre-implementation activities: discussion, estimation, design
- In addition, the DOD limits the cost of rework once a feature receives “done”
- Lastly, having an explicit contract limits the risk of misunderstanding and conflict between the development team and the customer or product owner
Get certified and unlock more opportunities. Practice and Validate your skills to become a Certified Agile Testing Professional Now!
