This repository has been archived by the owner on Dec 19, 2017. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 74
Definition of Done
Ian Wehrman edited this page Jun 12, 2015
·
1 revision
The following lists are candidates for our team's "Definition of Done"; i.e., what it means for a user story and sprint to be considered complete.
- User story is fully coded and documented internally
- Source code passes JSHint and JSCS grunt tasks
- Code has been reviewed by one other engineer
- Unit tests are written and all pass
- All bower dependencies are updated
- Smoke tests are added if necessary and pass
- Performance tests pass
- There are no open high-severity bugs
- Scenario testing completed by another person (engineer, PO, etc)
- Inform PgM about new third-party dependencies, or changes involving encryption
- Send an email DL-Playground-Dev to inform stakeholders of the new feature
- All bugs for all stories completed in the sprint are closed (or given an exception by QRB)
- All open bugs have been reviewed by QRB
- All unit, extension, and client & server smoke tests for the entire product pass on all platforms
- Performance tests have been run and the results have been recorded
- Release notes updated with information on features added, bugs fixed in the sprint, and major known issues
- README reviewed and any stale information updated
- All unnecessary branches deleted from Github repos
- Integrate Github
masterinto P4 (include git hash to the p4 check in comment) - Make brief screen recording of new features (if user facing). Add link to User Story Screen Recordings wiki page, and send out in a sprint DoD email.