- Agile Tutorial
- Agile - Home
- Agile - Primer
- Agile - Manifesto
- Agile - Characteristics
- Agile - Daily Standup
- Agile - Definition of Done
- Agile - Release Planning
- Agile - Iteration Planning
- Agile - Product Backlog
- Agile - Useful Terms
Agile - Definition of Done
The definition of done for User Story, Iteration, and Release is given below.
A user story is a requirement which is formulated in a few sentences in everyday language of an user and it should be completed within an iteration. A user story is done when
- All the related code have been checked-in.
- All the unit test cases have been passed.
- All the acceptance test cases have been passed.
- Help text is written.
- Product Owner has accepted the story.
An iteration is a time boxed collection of user stories / defects to be worked upon and accepted within the release of a product. Iterations are defined during iteration planning meeting and completed with an iteration demo and review meeting. An iteration is also termed as a sprint. An iteration is done when
- Product backup is complete.
- Performance has been tested.
- User stories have been accepted or moved to the next iteration.
- Defects have been fixed or postponed to the next iteration.
A release is a major milestone that represents an internal or external delivery of working, tested version of the product/system. A release is done when
- System is stress tested.
- Performance is tuned.
- Security validations are carried out.
- Disaster recovery plan is tested.
Kickstart Your Career
Get certified by completing the courseGet Started