Definition of Done

1. The code related to the story has been reviewed by at least one developer
2. The result of the story is deployed on a server (could be dev, int, or prod)
3. The user story defined in the story has been run successfully by a C2C developer and by the C2C-side internal reviewer (usually the Product Owner) on a staging server. If any HTML / CSS / JS is modified, the user story should be run in the major browsers. The C2C team must indicate in the story if this is the case so that the C2C-side internal reviewer can act accordingly.
4. All technical documentation or other wiki pages are updated accordingly.
5. New features usage are documented in the User documentation.
6. The feature is checked against the Testing Framework to determine the possible fallout of the change, when writing tests is easy (fast). F.e. a task of 10 minutes can have tests writing of 30 minutes, but a task of 1 day should have tests writing for approx. 2h.