The standards by which we define "done" for sprint functionality is key to the success of iterative, incremental development. Functionality that meets these standards at the end of a sprint will be considered potentially release-able and demoed at the Sprint Review.
Two types of people attend Daily Standup: Pigs and Chickens
A chicken and pig were walking down the street. The chicken said to the pig, "lets open a restaurant." The pig said, "Ok, what should we name it." The chicken said, "How about "Bacon and Eggs"." The pig said, "No way … I'd be committed but you would only be involved ."
Only functionality that meets “Done” criteria is demoed
Team declares what they committed to doing in the Sprint and did not get done
Feedback from customers and stakeholders drives design changes for future sprints
Sprint Review User Story Doneness Checklist User documentation complete and checked in. All UI labels ready for localization vendors. Usability testing scheduled when necessary, and feedback incorporated into backlog. UE has reviewed any new features; P1 and P2 UI bugs fixed. Performance/scalability impact ascertained and sys testing scheduled if required. All resolved bugs verified and closed. 100% of test cases logged in QA Tracker and executed in a QA environment, and all P1/P2 cases passing. Code Coverage of 70% (or as agreed with team) No open P1 & P2 bugs No open regressions. Automated tests written and reviewed for all regressions. Code checked in and follows department standards. BT & Profile Perm Setup Page Handshake POC Done Criteria