Skip to content
PMPCAPM

Sprint Planning

Sprint Planning is the Scrum event that initiates each Sprint by defining the Sprint Goal, selecting Product Backlog items to work on, and creating an actionable plan for delivering the Increment.

Share:

Know it well enough for the exam? Questions on Sprint Planning are scenario-based, not definitional.

Practice it free

Explanation

Sprint Planning addresses three topics: why the Sprint is valuable (the Sprint Goal), what can be done during the Sprint (selecting backlog items), and how the chosen work will get done (creating a plan). The entire Scrum Team collaborates in Sprint Planning, and the Product Owner ensures the most important items are ready for discussion.

The Sprint Goal is crafted during Sprint Planning and gives the team a coherent objective. The Developers then select items from the Product Backlog that they forecast they can complete. This selection is based on past performance (velocity), current capacity, and the Definition of Done. The Developers decompose the selected items into tasks and create the Sprint Backlog.

Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The quality of Sprint Planning directly impacts the team's ability to deliver a valuable Increment.

Key Points

  • •Addresses why (Sprint Goal), what (selected items), and how (plan for delivery)
  • •Timeboxed to eight hours maximum for a one-month Sprint
  • •The entire Scrum Team participates
  • •Results in the Sprint Backlog with a clear Sprint Goal

Exam Tip

Sprint Planning produces three outputs: the Sprint Goal, the set of selected Product Backlog items, and the plan for delivering them. Know all three.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Part of

Agile & Hybrid

Study full domain →

Practice Sprint Planning

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.