What is definition of done? • Outlines the criteria for the product owner to accept the work completed in a sprint. • Serves as exit criteria or a governing agreement that guides all development activities. • Defines potentially implementable functionality, so it must include QA testing. • Is defined by the scrum team and applies to the entire sprint or release. • May be changed over time as the teams matures and based on the type and scope of the sprint. • Is different from acceptance criteria, which applies to a single user story or product backlog item. Tasks complete Code complete Meets acceptance criteria Configuration is checked in Code review performed Enterprise standards met No unacceptable blockers Product owner approval Automated test scripts
Examples User story (during Sprint) Unit- and regression-tested (when applicable), and all tests passed Release All code for release deployed to production Test scripts executed; no blockers or critical defects Smoke tests passed exist; no alerts or expectations existing in PDC Code is peer-reviewed Product Owner has accepted release contents All rules are documented Release notes updated Specifications are attached to rules and are marked End-to-end, or global, validation performed to as complete ensure rules can coexist in production Rule is checked into release ruleset End-user documentation written and reviewed Technical documentation updated if appropriate Product rule updated when applicable PDC Improvement plan reviewed for release No unjustified warnings Design review performed