SCRUM
Roles
Scrum recognizes only three distinct roles
Product Owner
Scrum Master
Team Member
Product Owner
Holds the vision for the product
Represents the interests of the business
Represents the customers
Owns the product backlog
Orders (prioritizes) the items in the product backlog
Creates acceptance criteria for the backlog items
Is available to answer team members’ questions
Scrum Master
Scrum expert and advisor
Coach
Impediment bulldozer
Facilitator
Team Member
Responsible for completing user stories to incrementally increase the value of the product
Self-organizes to get all of the necessary work done
Creates and owns the estimates
Owns the “how to do the work” decisions
Avoids siloed “not my job” thinking
Scrum Artifacts
The Product Backlog
Each story in the product backlog should include:
Which users the story will benefit (who it is for)
A brief description of the desired functionality
The reason that this story is valuable (why we should do it)
An estimate as to how much work the story requires to implement
Acceptance criteria that will help us know when it has been implemented correctly
The Sprint Backlog
Is the team’s to do list for the sprint
Has a finite life-span (length of the current sprint)
Includes all of the stories and tasks that the team has committed to delivering this sprint
Is fixed in terms of time and commitment
Burn Charts
Task Board
Tasks are visible to everyone from across the room
Visibility so that no tasks will be forgotten
The simplest task board consists of three columns
To Do
Doing
Done
Provides visibility regarding the state of each task
Helps the team inspect their current situation and adapt
Helps stakeholders see the progress that the team is making
Definition of Done
Decided by the team
Should be the same as other teams working on the same backlog
Avoid ambiguity as to the state of a story
Should include all...