Optimizing User Story Workflow: Definitions, Checklists, and Criteria
"Learn how to enhance team workflow with clear definitions of ready and done, along with comprehensive checklists and criteria for user story completion. Improve your agile processes today!"
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
Definition of Ready (DoR) Definition of Done (DoD) | I m p r o v e | I n n o v a t e | D i g i t i s e | www.business-analysis.com.au 1
Definition of Ready Checklist Overview The Definition of Ready checklist is used by teams to make the criteria for completed User Stories and Sprints explicit and visible to everyone. The User Stories and Sprints must meet the agreed criteria prior to being accepted for any upcoming iterations. The criteria is based of the INVEST matrix- this is a widely accepted set of criteria used to asses the quality of a User Story being proposed for iterations. If your User Stories don t meet this criteria the team should either re-word it or even, consider a full re-write of the User Story. A User Story should be aligned to the following: I ndependent (of all others) N egotiable (not a specific contract for features) V aluable (or vertical) E stimable (to a good approximation) S mall (so as to fit within an iteration) T estable (in principle, even if there isn t a test for it yet) The Definition of Ready checklist is a baseline guide only. Work with your team to agree on The list of tasks or change the baseline list to meet your teams needs. | I m p r o v e | www.business-analysis.com.au I n n o v a t e | D i g i t i s e | 2
Definition of Ready User Story Sprint User Story defined The Sprint Backlog is prioritised The Spring Backlog contains all defects, User Stories and other work that the team is committing to User Story dependencies identified User Story sized by Delivery Team No hidden work All team members have calculated their capacity for the Sprint Scrum Team accepts User Experience artifacts Performance criteria identified, where appropriate Full-time on project = X hours per day The person who will accept the User Story is identified All User Stories meet Definition of Ready The team has a good idea what it will mean to Demo the User Story | I m p r o v e | www.business-analysis.com.au I n n o v a t e | D i g i t i s e | 3
Definition of Done Checklist The Definition of Done checklist is used by teams to ensure agreement of the criteria that must be met for a User Story to be considered done . Failure to meet this criteria at the end of team sprint would imply that the User Story cannot be released into production as a part of the Release phase. The checklist helps to define the teams understanding of the tasks required to be completed for a user story to be considered for release post sprint. The definition of done is very vague so the checklist ensures that all tasks have been considered not just the development of the feature that is documented within the User Story. The Definition of Done checklist is a baseline guide only. Work with your team to agree on The list of tasks or change the baseline list to meet your teams needs. | I m p r o v e | www.business-analysis.com.au I n n o v a t e | D i g i t i s e | 4
Definition of Done User Story Sprint Release Satisfied DoD for each sprint within the release Produced code for presumed functionalities Satisfied DoD for each sprint within the release Production environment is ready Assumptions of US met Marketing feedback is complete CI/CD verified and working Legal and compliance review is complete Project builds without errors User guides have been socialised with the right users User help guide created or completed Unit tests written and passing Roll back process is tested and documented Project deployed on the test environment identical to production platform Training video created or updated Smoke testing scenarios are written and ready Tests on devices/browsers listed in the project assumptions passed Refactoring is complete Frontline customer teams are trained and ready QA (Quality Assurance) session performed Configuration or build changes documented Release communications sent to users Issues from QA session resolved Performance testing is complete All stakeholders have signed off the proposed release Any configuration or build changes documented Security testing is complete Sprint marked as ready for deployment Documentation updated (if exists) PCR (Peer Code Review) performed | I m p r o v e | www.business-analysis.com.au I n n o v a t e | D i g i t i s e | 5
