Quality products delivered are the No. 1 driver for success. No doubt, we live in an imperfect world: People make mistakes and machines break. The goal is to minimize these things happening but you'll have to focus on quality. Relentlessly. These are a few ways in which you can do that....
Definition of Done:
When a backlog item is ‘done’, everyone must know what ‘done’ means.
Examples:
1. Code is peer-reviewed
2. Code is deployed to test environment
3. Feature is tested against acceptance criteria
4. Feature passes regression testing
5. Feature passes smoke test
6. Feature is documented
7. Feature ok-ed by UX designer
8. Feature ok-ed by Product Owner
Definition of Ready:
Having a Definition of Ready means that stories must be immediately actionable. The Team must be able to determine what needs to be done and the amount of work required to complete the User Story or Item.
1. Story must be written as a user story (i.e. “As a <kind of user> I want <feature> so that <benefit>”)
2. Acceptance criteria must exist and be understood by team
3. Story has been estimated by the team
4. UX sketches exist, where appropriate, and are understood by team
5. Performance criteria exist, where appropriate, and are understood by team
6. The team understands how to demo the feature
Release Retrospectives/Strategy Improvement Talks
During the Retrospective, the team discusses:
What went well in the release?
What could be improved?
What will we commit to improve in the next release?
The lead encourages the Team to improve its development process and practices to make it more effective and enjoyable for the next release. During each Retrospective, the Team plans ways to increase product quality by improving work processes or adapting the definition of “Done” if appropriate and not in conflict with product or organizational standards.
By the end of the Retrospective, the Team should have identified improvements that it will implement in the next release. Implementing these improvements in the next release is the adaptation to the inspection of the Team itself.
Although improvements may be implemented at any time, the Retrospective provides a formal opportunity to focus on inspection and adaptation.
Comments