Sprint Planning: From Product Goal to Sprint Goal and Sprint Backlog

From Product Goal to Sprint

Sprint Planning turns the broad Product Goal into a concrete, short-term plan for one Sprint. It links long-term direction to near-term action.

Two Anchor Definitions

Product Goal: "The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against."

Sprint: "Sprints are the heartbeat of Scrum, where ideas are turned into value."

Three Core Questions

Sprint Planning answers: 1) Why is this Sprint valuable? 2) What can be done in this Sprint? 3) How will the chosen work get done?

Timebox and Attendees

Timebox: up to 8 hours for a one-month Sprint. Attendees: the entire Scrum Team; stakeholders may be invited but do not make decisions.

Not a Negotiation

Sprint Planning is not management vs. Developers. It is an internal Scrum Team event to decide a realistic, valuable Sprint plan.

Sprint Goal: Canon

Sprint Goal: "The Sprint Goal is the single objective for the Sprint." It gives the Sprint focus and direction.

Sprint Backlog: Canon

Sprint Backlog: "The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how)."

Single Objective, Many Items

The Sprint Goal is one coherent objective. Many Product Backlog items may contribute, but there is only one Sprint Goal per Sprint.

Three Parts: Why, What, How

Exam tip: if an option for Sprint Backlog misses the Sprint Goal, the selected items, or the actionable plan, it is incomplete.

Ownership and Adaptation

Developers own and adapt the Sprint Backlog. They update it as they learn, while keeping the Sprint Goal intact.

Developers: Canon

"Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint."

Who Attends

The entire Scrum Team attends Sprint Planning: Product Owner, Scrum Master, Developers. Others may be invited for advice.

Deciding the Why

Product Owner proposes how the product could increase value; the whole Scrum Team collaborates to craft the Sprint Goal.

Deciding the What

Developers decide how much work to pull into the Sprint. PO clarifies value but cannot force extra scope.

Deciding the How

Developers design the actionable plan. They own the "how" of the work; external parties do not dictate it.

Scenario Setup

Product: food delivery app. Product Goal: enable real-time order tracking to boost satisfaction by 15%. Sprint length: 2 weeks.

Step 1: Why This Sprint Is Valuable

PO wants customers to see at least basic status updates. Team crafts the Sprint Goal: "Provide customers with live status updates for their active orders."

Step 2: What Can Be Done

Developers select: push notifications for key events and minimal API changes to support them. The full map is deferred.

Step 3: How It Gets Done

Developers plan tasks: design events, implement backend, update apps, test flows. This actionable plan is part of the Sprint Backlog.

Link Back to Product Goal

The Sprint Goal clearly advances the Product Goal, even though not all tracking features are delivered yet.

Empiricism in Sprint Planning

"Scrum is founded on empiricism and lean thinking." Planning is based on what is known, with room to inspect and adapt.

Plan by Capacity, Not Wishful Thinking

Developers use past throughput, skills, and risks to decide how much work to pull, aligned with the Definition of Done.

Dealing With Uncertain Items

Large or unclear items are split or sliced. Developers avoid filling the Sprint with vague, high-risk work.

Learning as a Goal

When uncertainty is high, a Sprint Goal can focus on learning that still advances the Product Goal.

Flexibility Within the Sprint

The plan (tasks, design) can change as long as the Sprint Goal stays intact. Exam answers favor adaptability over rigid scope.

Your Product Goal

Product Goal: launch a basic analytics dashboard that helps sellers understand monthly sales and refund trends.

Backlog Snapshot

Items: 1) data model, 2) metrics API, 3) dashboard UI, 4) CSV export, 5) role-based access control.

Task 1: Craft a Sprint Goal

Write a single-objective Sprint Goal for a 2-week Sprint that advances the Product Goal. Avoid listing items.

Task 2: Choose Supporting Work

Select which items or slices you would include to support your Sprint Goal, given moderate capacity.

Self-Check

Does your Sprint Goal connect to the Product Goal, allow flexibility in tasks, and lead to a usable Increment?

Scrum Team Focus

"The Scrum Team is a cohesive unit of professionals focused on one objective at a time, the Product Goal." Sprint Planning aligns them for this Sprint.

Developers Own the Plan

Developers create and update the actionable plan, negotiate scope when needed, and use the Sprint Backlog daily to inspect and adapt.

Trap 1: Frozen Backlog

On the exam, reject any option that says the Sprint Backlog cannot change after Sprint Planning.

Trap 2: Optional Sprint Goal

There is always one Sprint Goal. It is not optional, and it is not a list of unrelated objectives.

Next Steps in Your Path

Use the next Skarp diagnostic and mock exam to pressure-test these ideas; your spaced review will reinforce the key definitions.