Scrum Meetings

Use the space bar or right arrow for next slide,
left arrow to back up.

Kinds of Meetings

Participants: the team
Duration: 15 minutes
Format: stand-up meeting (no PowerPoint!)
Same time and place, every day
Objective: determine what to do this day
Structure:
- Each member reports (only):
  1. What have I done since the last meeting?
  2. What do I hope to do by the next meeting?
  3. What blocks or impediments are in my way?
Result:

Participants: the team and the Product Owner
Objective: determine whether the product is acceptable
Structure:
- Team describes each of the features/stories/pieces implemented
- Users provide feedback on the pieces
Result: Stories are accepted as completed, or rejected
- Uncompleted stories may be dropped, or recycled, possibly with changes

A workshop (typically, an entire day)
Participants: the team, including Scrum Master
Objective: continuous process improvement
Identify adjustments that will make the next Sprint better
Structure:
- Facts: What happened? Each team members tells about the high and low points of the Sprint
- Positives: What aspects worked well?
- Improvement: What could be done to improve the project?
- Control: Who has the authority to make each improvement (inside/outside team)?
- Prioritization: What are the top priorities?
Output = two lists of action items (with stated goal/reason for each action)
- One for the team (inside)
- One for the Scrummaster (outside: involving the rest of the organization)
Result: Consensus on what to do next
Critical: Feedback must be followed up, or the meeting will be a waste, and the next will not be taken seriously

I synthesized these notes from several sources, including the following: