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 Planning

Sprint Planning is:

  • time-boxed to max 8 hours for a one-month Sprint (or less for shorter Sprints)

Entire Scrum Team:

  • plans the work to be done in the Sprint collaboratively

Scrum Master:

  • ensures the event takes place
  • ensures attendants understand its purpose
  • teaches the team to keep it within the time-box

Sprint Planning answers 2 questions:

1. What can be done this Sprint?

Inputs

  1. Product Backlog
  2. Latest “Done” product Increment
  3. Past performance of Development Team
  4. Projected capacity of Development Team in this Sprint

Outputs

  1. Sprint Goal
  2. Product Backlog items selected for the Sprint

Guidelines

Product Owner:

  • discusses the objective to achieve in the Sprint
  • discusses the items from Product Backlog that would achieve the objective

Development Team:

  • forecasts the functionality to be developed during the Sprint
  • assess what it can accomplish in the Sprint
  • selects Product Backlog items for the Sprint

Entire Scrum Team:

  • collaborates on understanding the work of the Sprint
  • crafts a Sprint Goal
    • an objective that will be met in the Sprint
    • a guidance to Development Team on why it is building the Increment

2. How will the chosen work get done?

Inputs

  1. Sprint Goal
  2. Product Backlog items selected for the Sprint

Outputs

  1. Sprint Backlog that includes:
    • Product Backlog items selected for this Sprint
    • a plan on how to deliver the product Increment to accomplish the Sprint Goal

Guidelines

Development Team:

  • decides how it will build the functionality into a “Done” product Increment
  • starts by designing the system and the work needed to deliver a working product Increment
  • plans work (work size estimation) enough to forecast what it believes it can do in the Sprint
  • decomposes planned work enough for the first days of the Sprint
  • self-organizes to undertake the work
  • renegotiates selected Product Backlog items with Product Owner, if too much or too little work
  • may invite other people to attend to provide technical or domain advice

Product Owner:

  • clarify the selected Product Backlog items and make trade-offs

Sprint Goal

Sprint Goal is:

  • an objective set for the Sprint that can be met through the implementation of Product Backlog
  • a guidance to Development Team on why it is building the Increment
  • created during Sprint Planning by entire Scrum Team

Sprint Goal gives Development Team:

  • some flexibility on the functionality and technology implemented within the Sprint
  • a coherence that causes Development Team to work together rather than on separate initiatives

Development Team alawys keeps the Sprint Goal in mind, as it works in the Sprint.


Read the full text in The Scrum Guide.

In 2-Minute Scrum for Busy Teams series