Scrum Guide - Sprint Planning Flashcards

Study Notes

Sprint Planning Overview

Sprint Planning is the event where the work for the upcoming Sprint is planned.
The entire Scrum Team collaborates to create the plan during this meeting.

Duration and Time-Boxing

Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint.
For shorter Sprints, the duration of the planning meeting is proportionally shorter.

Role of the Scrum Master

The Scrum Master facilitates the Sprint Planning event, ensuring it occurs and that participants understand its purpose.
The Scrum Master advises the Scrum Team on adhering to the time-box during planning.

Key Questions Answered

Sprint Planning addresses two key questions:
- What can be delivered in the upcoming Sprint's Increment?
- How will the necessary work to deliver that Increment be accomplished?

Forecasting Potential Work

The Development Team forecasts the functionalities to be developed based on the discussed objectives and Product Backlog items.
The Product Owner shares the Sprint objectives and relevant items from the Product Backlog during planning.
The collaboration within the Scrum Team helps to comprehensively understand the work required for the Sprint.

Inputs to Sprint Planning

Essential inputs for Sprint Planning include:
- The Product Backlog
- The most recent product Increment
- The Development Team's projected capacity
- Historical performance data of the Development Team

Creating the Sprint Goal

The Development Team selects Product Backlog items and creates a Sprint Goal during the planning phase.
The Sprint Goal serves as a guiding objective for the team, clarifying why the Increment is being built.

Development Team's Approach

Post-selection, the Development Team outlines how to achieve the functionality in a "Done" Increment.
The collection of selected Product Backlog items and the plan to deliver them forms the Sprint Backlog.

Planning Work Details

The Development Team begins with system design and identifying tasks to convert Product Backlog items into a working product Increment.
They estimate effort and size for the various tasks but ensure sufficient work is planned to meet Sprint capacity forecasts.
Work planned for early Sprint days is broken down to smaller units, typically a day or less.

Self-Organizing Team Dynamics

The Development Team is responsible for self-organizing the work outlined in the Sprint Backlog throughout the Sprint.
The Product Owner may assist in clarifying tasks or negotiating trade-offs as needed.
If work volume fluctuates, the Development Team can re-negotiate selected items with the Product Owner.

Final Outcomes of Sprint Planning

By the end of Sprint Planning, the Development Team should clearly articulate how it plans to achieve the Sprint Goal and deliver the expected Increment while operating as a self-organizing team.

Description

Test your knowledge of Sprint Planning through these flashcards. This quiz covers key concepts such as who participates in the planning process and the timing of the meetings. Perfect for those studying Scrum methodologies and frameworks.