-
Notifications
You must be signed in to change notification settings - Fork 147
Definition Of Done
scolsonlinagora edited this page Sep 8, 2015
·
15 revisions
The team agrees on these Definition Of Done (also named DoD). There can be several level and area for Definition Of Done
## DoD ready for dev Dev have all information to work on the task without ambiguity.
QA have all information to work on the task, meaning only test what is relevant for this task. A developer must ask himself if the following points are clear and defined in the ticket and not subject to interpreting; If they aren't, this must be clarified
- Dev done I have done what the Description/Acceptance Criteria asks for. If not, explain what.
- Comment All comments answered
- CI All PR merged, Build success deployed on a pre-prod. If not explain where this can be tested
- Impact Explain what features my change may impact in the all product. This information will be used to help QA to do only relevant tests
- Tests done What did you test to validate the fix and which environment did you use
- New bugs If new bugs have been encountered, jira(s) opened for them
- Now you can click on "Resolved" with your comment
There is no need to use a template and answer all these questions. Please just add in a comment what will be useful.