Three Roles: Product Owner, Scrum master, Team
The Product owner: Own and prioritizes the Product Backlog
- defines and prioritizes features--owns the gathering of requirements
- agrees to iteration ground rules--set length of calendar time for sprint (2,3,4 weeks typical)
- does not interfere with sprint(no scope creep)
- can pull the plug at any time(has the power)
- honors rules and the scrum process during sprints
Scrum Master: A Boundary Manager, Facilitates the Scrum process, Not a traditional Project manager
- supports the team, facilitates the daily scrum meeting.
- asks each developer: what do you do yesterday? what are you doing today? what is in your way?
- listens and watches carefully during scrum meeting
- pays carefull attention to non-verbal cues
- removes impediments in way of team
- secures resources(monitors, rooms, etc)
- communicates to Product Owner
The team
- participates in design to gain understanding of problem/solution space
- selects subset of prioritized product backlog for sprint comment: estimates the effort, fills the timebox with work, commits to the work as a team
- self organizes: everyone commits to all tasks neccessary during the sprint, determines the nature of self-organization
- teams select work for each sprint
- teams self-organize
- teams have a velocity
Team velocity: how much work the team can average per iteration, for that team
- each time has a personality
- each team is unique
- teams velocity becomes very predictable over time
Three ceremonies: Sprint Planning, Daily Scrum, Sprint Review(retrospective)
ceremony #1: Sprint Planning Meeting
- Product Owner reviews: vision, roadmap, release plan
- team reviews: estimates for each item on backlog that is a candidate for the sprint
- team pulls the work: from the Product Backlog onto the Sprint Backlog
Ceremony #2: The Daily Scrum
- By and for the Team
- Other may attend and NOT speack
- Team members speack, others listen
- Team stays on task with the 3 questions, devergences are addressed offline outside of this meeting
- visibility, clear understanding on a day-by-day basis
Product owners know the score on a daily basis, can pull the plug at any time
Ceremony #3: Sprint Review Meeting
Part 01: Product Demo
Led by Product Owner
Part 02: Sprint Retrospective
Led by Scrum Master
What worked?
What didn't?
What adjustments can we make now?
Three Artifacts: Product Backlog, Sprint Backlog, Burndown Chart
Artifact #1: Product Backlog
- A list of features, prioritized by business value
- Each feature has an associated estimate, provided by the ACTUAL team who will do the work
- Backlog items come in from deverse sources, including the Team
Artifact #2: Sprint Backlog
- Topmost subset of the Product Backlog, loaded onto the Sprint's "timebox"
- usually has more detail attached, including planned hours and primary person responsible to do the work during the Sprint
- Is the list of work the Team is addressing during the current Sprint
Artifact #3: Burndown Chart
- Provides visibility into the Sprint
- Illustrates progress by the team
- Work on the Horizontal, Time on the Vertical
Three Best Practices: User Stories, Planning Porker, Scrum Board
Best Practices #1: User Stories
- Plan-english requirements, written on common 3*5 index cards
- Form: As a type of user, I want to [perform a specific action] such that [result]
- Example: "As a web user, I want to make a reservation, such that I may secure my lodging"
- Stories that are big are called EPICS
- Acceptance criteria goes on card back
Best Practice #2: Planning Poker
- A way for the team to do estimates
- Each participant has cards numberd 1,2,3,5,8,13,21
- Values represent 'story points' of effort
- Players discuss feature, then throw down a card together
- Differences are noted and discussed, then process repeats till a concensus estimate is formed
Best Practice #3: Scrum Board
- Scrum Board is a rows-and-columns depictions of work-in-progress
- Items of work are rows, work status lables are columns
- Work is addressed from top to down
- Work migrates from left to right on the board
