Definition of Done Definition of Ready

Definition of Done

• Code produced: All 'to do' items in code completed.
• Code commented, checked in, and run against the current version in source control.
• Peer reviewed (or produced with pair programming) and meeting development standards.
• Builds without errors.
• Unit tests written and passing.
• Deployed to the system test environment and passed system tests.
• Passed UAT (User Acceptance Testing) and signed off as meeting requirements.
• Any build/deployment/configuration changes are implemented/documented/communicated.
• Relevant documentation/diagrams produced and/or updated.
• Remaining hours for the task set to zero and the task closed.

Definition of Ready

• User Story is clear.
• User Story is testable.
• User Story is feasible.
• User Story defined.
• User Story Acceptance Criteria defined.
• User Story dependencies identified.
• User Story sized by the Development Team.
• Scrum Team accepts User Experience artifacts.
• Performance criteria identified, where appropriate.
• Scalability criteria identified, where appropriate.
• Security criteria identified, where appropriate.
• Person who will accept the User Story is identified.
• Team has a good idea of what it will mean to demo the User Story.