Definition of Ready Examples

• Business value is articulated and understood for the user story.

• User roles and personas for the story are understood.

• Enough acceptance criteria are defined for the development team to estimate and commit.

• The team agrees they can commit to the user story in a sprint.

• Acceptance criteria are clear and testable.

• Developers and QA have had a chance to discuss details, alternatives, and design options with the product owner and or BA.

• Unknown or risky aspects of the functionality are discussed, and spikes may be defined.

• The team agrees the story has feasible design options.

• Business rules, nonfunctional requirements, and a lo-fi mockup have been provided if needed as part of the acceptance criteria.

• Any dependencies have been identified.

• User experience is understood by the team.

• Performance criteria and nonfunctional requirements have been discussed.

• The team has an idea of how to demo the story and who to demo it for

Definition of Done Examples

• The code has been peer-reviewed.

• End-user training documentation and help information have been updated.

• The story functionality has been demonstrated to the product owner for feedback multiple times.

• The functionality has been demonstrated with a larger stakeholder group.

• The code has been checked.

• The team has documented what was built.

• QA has tested the user story and developed regression tests.

• Testing and automated test scripts have been completed and implemented into a test suite.

• Updated process assets, diagrams, models, and so on have been updated with what was implemented.

• Automated regression testing scenarios have been updated and added to the automation testing suite.