There are essential boundaries to how your scrum team works. Learn what boundaries to use to help them meet their goals.
- At this point, you should have your themes and features…broken down into user stories.…Also, you've estimated your stories using points…so you know about how much work is waiting to be done.…This is your product backlog.…Your next step is to create boundaries…that your team can use to complete this work.…These guidelines include the team's definition of done,…prioritizing your backlog,…and establishing your sprint cadence.…First, your team needs to define done for their stories.…
I know each story has its own acceptance criteria,…but this definition is a little bit more general.…This definition of done states the minimum requirements…for all stories.…Since these apply to everything in your backlog,…you don't want to repeat these things…in the AC of every story.…Creating this overarching definition of done helps save time…while allowing more precision in the story specific AC.…Examples of done criteria for all stories are…for a story on our team to be considered done,…it has been tested in the pre-release environment…
Lynda.com is a PMI Registered Education Provider. This course qualifies for professional development units (PDUs). To view the activity and PDU details for this course, click here.
The PMI Registered Education Provider logo is a registered mark of the Project Management Institute, Inc.
- Understanding the scrum approach to project success
- Solving project problems with scrum
- Establishing your scrum team
- Setting the vision for your project
- Writing user stories
- Setting boundaries for success
- Getting stories done in scrum
- Assessing the team