Don’t Butcher Your

Sprint Planning
The Sprint Planning is a core event that defines
how your customers’ lives will improve with the
following Increment.

Moreover, it is not rocket science:

(1) First, the Product Owner points to the

team’s Product Goal and introduces the
business objective of the upcoming Sprint.

(2) The Scrum Team then collaboratively

creates a Sprint Goal, considering who is
available and the target the team shall
accomplish.

(3) Next, the Developers forecast the work

required to achieve the Sprint Goal by picking
the right items from the Product Backlog and
transferring them to the Sprint Backlog.
(Alternatively, they create new work items.)

(4) Also, the Developers need to create a

preliminary “plan” on how to accomplish the
Sprint Goal.
1. Business Objective

It is the Product Owner’s prerogative to define

the business goal of the upcoming Sprint.

However, it is not identical to the Sprint Goal.

Check out the free Scrum Anti-Patterns Guide.

 2. Definition of Done

Consider your Definition of Done to understand

the magnitude of work associated with the
planned or suggested outcome of the Sprint
before creating a Sprint Goal.

Check out the free Scrum Anti-Patterns Guide.

3. Capacity and
Past Perfomance

Consider the classic questions:

• Who will be available?
• What shall we work on?
• Are webiting off too much?

Check out the free Scrum Anti-Patterns Guide.

 4. Garbage in,
Garbage out

An inferior or not existing Product Goal and a

corresponding, low-quality Product Backlog
won’t allow you to deliver a great Sprint Goal.

Check out the free Scrum Anti-Patterns Guide.

 5. Retrospective
Commitments

Remember to honor your commitments from

the last Retrospective!

Check out the free Scrum Anti-Patterns Guide.

 How to Download a
PDF from your
LinkedIn Feed:

(1) Hover with the pointer over the

document. In the lower right corner, click
on this icon:

(2) Once you are in full-screen mode,

download the PDF by clicking this icon

in the upper right corner.

 Join 49,000 Peers
and Subcribe to the
Food for Agile
Thought Newsletter

https://bit.ly/m/StefanW
 6. Sprint Goal

Collectively, as a Scrum team, create a

meaningful Sprint Goal, delivering value to
customers and the organization.

Check out the free Scrum Anti-Patterns Guide.

 7. Forecast

The Developers collaboratively forecast the

work them consider necessary to accomplish
the Sprint Goal.

Check out the free Scrum Anti-Patterns Guide.

 8. Sprint Backlog
Finally, you created your Sprint Backlog:

• As a Scrum team, you agreed on a

valuable Sprint Goal — the WHY.

• The Developers identified work items

necessary to accomplish the chosen goal
— the WHAT.

• Moreover, they developed a

(preliminary) on plan on how to deliver
the Increment — the HOW.

Check out the free Scrum Anti-Patterns Guide.

 Coming soon…

Preorder your copy now: https://geni.us/wtS2aa

(Includes affiliate link to your local Amazon store.)
Get Your Free Copy of
the Scrum Anti-
Patterns Guide:
https://age-of-product.com/scrum-
anti-patterns/
 Connect with me:

https://bit.ly/m/StefanW