Too long, didn’t read?

The Scrum Guide is short, concise and informative. I encourge you to read it. But if it’s too long to you, or you need to onboard a busy team, follow me on my new blog series 2-Minute Scrum for Busy Teams — a bite-size, per-chapter, bullet-point summary of The Scrum Guide.

Sprint Review

Sprint Review:

  • inspects - the Increment
  • adapts - the Product Backlog if needed

  • max 4 hours for one-month Sprints
  • held at the end of the Sprint
  • an informal meeting, NOT status meeting
  • intended to elicit feedback and foster collaboration

Scrum Master:

  • ensures the event takes place and attendees understand its purpose
  • teaches everyone to keep it within the time-box

Product Owner:

  • invites attendees - Scrum Team and key stakeholders
  • explains what Product Backlog items have been “Done” and not “Done”
  • discusses Product Backlog as it stands
  • projects likely target and delivery dates based on progress to date (if needed)

Development Team:

  • discusses:
    • what went well during the Sprint
    • what problems it ran into
    • how problems solved
  • demonstrates “Done” work
  • answers questions about the Increment

Scrum Team and stakeholders:

  • collaborate about what was done in the Sprint
  • collaborate on what to do next, which becomes valuable input to next Sprint Planning
  • review timeline, budget, potential capabilities, marketplace to answer: what is the most valuable thing to do next


  • Revised Product Backlog:
    • defines the probable Product Backlog items for next Sprint
    • may be adjusted overall to meet new opportunities

Read the full text in The Scrum Guide.

In 2-Minute Scrum for Busy Teams series