-
Notifications
You must be signed in to change notification settings - Fork 147
Definition Of Done
Stéphane Colson edited this page Jun 10, 2016
·
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 Developer must have all information to work on the task without ambiguity. If dev have any doubt about what is asked, don't shut up and ask to be sure of what you have to do !
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(s) may impact in the all product. According to your knowledge of the software/architecture, what are the possible side effects of your code change ?
- Tests done What did you test to validate the fix and which environment did you use. If it impacts smartphone (or tablet) view, then a real smartphone (or a real tablet) must have been used to validate the fix.
- New bugs If new bugs have been encountered, jira(s) opened for them
- If this issue will be fixed when another issue will be done, then don't mark this one "Resolved" but add a comment and a link "Blocked by" to the ticket.
- If this is a reopen, don't edit previous DoD comment but add a new one explaining what you've done
- Click on "Resolved" with your comment only if everything is OK and can be tested
There is no need to use a template and answer all these questions. Please just add in a comment what will be useful.