Sprint Planning
PSM I PSM I · Scrum Events
Sprint Planning initiates the Sprint by laying out the work to be performed. The resulting plan is created by the collaborative work of the entire Scrum Team — not by the Product Owner alone, not by the Scrum Master, and not by the Developers in isolation. The event is timeboxed to a maximum of eight hours for a one-month Sprint; for shorter Sprints it is usually shorter. The eight-hour figure is a maximum, not a target: a team running two-week Sprints will typically plan in far less time, and the exam tests the maximum, so remember that eight hours belongs to the one-month case. The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal, and the Scrum Team may invite other people to attend to provide advice — but the plan itself is the Scrum Team's work.
Sprint Planning addresses three topics, in order: why, what, and how. The first topic — why is this Sprint valuable? — produces the Sprint Goal. The Product Owner proposes how the product could increase its value and utility in the current Sprint, and the whole Scrum Team collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Sprint Goal must be finalized before the end of Sprint Planning; it is not something the team works out later. The second topic — what can be Done this Sprint? — is where the Developers select items from the Product Backlog. They select items in discussion with the Product Owner, and may refine items during the event to increase understanding and confidence. Selecting how much can be completed within a Sprint is challenging, and the Developers draw on their past performance, current capacity, and Definition of Done to judge it. The third topic — how will the chosen work get done? — is where the Developers plan the work: they decide how to turn the selected items into an Increment that meets the Definition of Done, often breaking items down into smaller work units of one day or less. The resulting plan — the Sprint Goal, the selected items, and the plan for delivering them — is the Sprint Backlog.
Two points about Sprint Planning are tested constantly. The first is who decides what: the Developers decide how much work they can take on, and nobody else decides it for them. A Product Owner who insists the team take on more than it believes it can complete is breaking the framework, however reasonable the pressure seems. The second is the Sprint Goal: it is created during Sprint Planning, it is the commitment for the Sprint Backlog, and it gives the Sprint coherence. A Sprint without a clear goal is just a collection of tasks, and the team has no basis for making trade-offs when things change. The exam often presents a Sprint Planning scenario where the team selects items without agreeing a goal — the correct response is that the goal must be finalized before the event ends, because the goal is what the team commits to, not the list of items.
What Sprint Planning is not
Sprint Planning is not a status meeting, not a detailed design session, and not a negotiation where the Product Owner dictates scope. The plan the Developers create does not need to be a complete upfront design — it needs enough detail that the Developers can inspect their progress in the Daily Scrum and adapt as they learn. Items are often broken down during the Sprint itself as understanding grows. Sprint Planning is also not the place to re-estimate the entire Product Backlog or to debate the Product Goal at length; refinement is an ongoing activity that happens throughout the Sprint, and Sprint Planning builds on the refinement already done. Teams that arrive at Sprint Planning with unrefined items at the top of the backlog will struggle, which is why the Product Owner's preparation — ensuring attendees are ready to discuss the most important items — matters so much.
Worked scenario
A Scrum Team arrives at Sprint Planning. The Product Owner presents the top of the backlog and proposes that the Sprint's value lies in making the checkout flow usable for a new market. The team discusses this and agrees a Sprint Goal: enable checkout for the new market. The Developers then select the items needed for that goal, judging from past performance that they can complete four of the five candidate items. They break the largest item into smaller pieces and sketch how the work will be done, including a testing approach. The Sprint Goal is written down and finalized before the event ends. This is Sprint Planning done well: why, then what, then how — with the Developers deciding the amount of work and the team as a whole owning the goal. If the Product Owner had instead arrived with a fixed list of items and no goal, the team would have a list of tasks but no shared purpose — and the first time something went wrong, there would be no goal to protect.
Common Sprint Planning problems
Sprint Planning goes wrong in predictable ways. The most common is arriving unprepared: the top of the Product Backlog is unrefined, items are too large or unclear, and the event becomes a refinement session instead of a planning session. The fix is ongoing refinement during the Sprint, so the top of the backlog is always ready. Another common failure is skipping the Sprint Goal: the team selects items without agreeing why the Sprint is valuable, and ends up with a list of tasks but no shared purpose. The fix is to start with why, every time, and finalize the goal before the event ends. A third failure is overcommitment: pressure from the Product Owner or stakeholders pushes the Developers to take on more than they can complete, and the Sprint ends with unfinished work and a missed goal. The fix is trust in the Developers' judgement about what can be Done, based on their past performance and capacity. The Scrum Master watches for all three patterns and coaches the team and the Product Owner toward better habits.
Exam traps to watch for
- Thinking the Product Owner decides how much work the team takes on. The Developers select the items and judge what can be Done, based on past performance, capacity, and the Definition of Done.
- Forgetting the Sprint Goal must be finalized before the end of Sprint Planning. A Sprint without a goal has no commitment and no basis for trade-offs.
- Quoting 8 hours for every Sprint. The 8-hour maximum applies to a one-month Sprint; shorter Sprints have shorter planning sessions.
- Treating Sprint Planning as a detailed upfront design session. The plan needs enough detail to inspect progress daily — it does not need to specify everything in advance.
Practice questions
Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.
Q1.What is the maximum timebox for Sprint Planning for a one-month Sprint?
Explanation: Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. Four hours is the maximum for the Sprint Review. Three hours is the maximum for the Sprint Retrospective. Fifteen minutes is the Daily Scrum.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q2.Sprint Planning addresses three topics. In what order are they addressed?
Explanation: Sprint Planning addresses why this Sprint is valuable (which produces the Sprint Goal), then what can be Done this Sprint (selecting items), then how the chosen work will get done (the Developers' plan). Any other order puts the goal or the selection in the wrong place.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q3.Who decides how many Product Backlog items the Developers select for a Sprint?
Explanation: The Developers select the items and judge what can be Done, drawing on past performance, current capacity, and the Definition of Done. The Product Owner proposes value and orders the backlog but does not decide the amount of work. The Scrum Master does not decide scope. Stakeholders do not select Sprint work.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q4.When must the Sprint Goal be finalized?
Explanation: The Sprint Goal must be finalized prior to the end of Sprint Planning — it is the commitment for the Sprint Backlog and the basis for the Sprint's work. Leaving it until the first Daily Scrum or the Sprint Review means the team starts the Sprint without its objective. It cannot stay open all Sprint.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q5.Who creates the plan that results from Sprint Planning?
Explanation: The plan resulting from Sprint Planning is created by the collaborative work of the entire Scrum Team. It is not the Product Owner's solo output, not the Scrum Master's plan, and not the Developers' plan awaiting approval — all three accountabilities contribute.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q6.During Sprint Planning, the Developers realize they need to break a large Product Backlog item into smaller pieces to understand it. What should they do?
Explanation: During Sprint Planning the Developers may refine items to increase their understanding and confidence before selecting them. Refinement is not banned from Sprint Planning — although most refinement happens as an ongoing activity, the event explicitly allows it. The Scrum Master does not break items down for the Developers. Selecting an item nobody understands is a recipe for a missed Sprint Goal.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q7.What is the Product Owner's responsibility in preparing for Sprint Planning?
Explanation: The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal. The Sprint Backlog is created during the event by the team, not written in advance by the Product Owner. The Sprint Goal is defined collaboratively, not decided alone. Estimating is the Developers' responsibility.
Exam objective: PSM I Focus Area: Managing Products with Agility — Product Backlog Management
Q8.A Product Owner insists the Developers take on six items in the Sprint, but the Developers believe they can only complete four. What is the correct outcome?
Explanation: Selecting how much can be completed within a Sprint is the Developers' decision, based on past performance, capacity, and the Definition of Done. The Product Owner does not outrank the Developers — there is no hierarchy in the Scrum Team. The Scrum Master does not decide scope. And Sprint selection is not decided by vote.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events
Q9.Which statement about the Sprint Planning timebox is TRUE?
Explanation: The 8-hour figure is a maximum for a one-month Sprint; for shorter Sprints the event is usually shorter. It is not exactly 8 hours in all cases. Sprint Planning does have a timebox — it is a timeboxed event like all Scrum events. And the figures are not reversed: 8 hours belongs to the one-month Sprint.
Exam objective: PSM I Focus Area: Understanding and Applying the Scrum Framework — Events