Sprint Planning is one of five events in Scrum. It helps the Scrum Team understand the work to be performed in the Sprint.
Like every event in Scrum, Sprint Planning is all about empiricism. Its purpose is for the team to inspect the Product Backlog and to create the Sprint Backlog. The Sprint Backlog represents the plan to achieve the Spring Goal and to create a potentially releasable Increment of work.
Sprint Planning is attended by the entire Scrum Team – the Product Owner, the Development Team and the Scrum Master. The Development Team may also invite other people to attend to provide technical, domain or business subject matter expertise.
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.
Sprint Planning answers the following:
The Product Owner can help to clarify the selected Product Backlog items and make trade-offs. If the Development Team determines it has too much or too little work, it may renegotiate the selected Product Backlog items with the Product Owner.
By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organising team to accomplish the Sprint Goal and create the anticipated Increment.
How do you write great User Stories?
Backlog Refinement is a critical part of good practice in Scrum. Refining the Product Backlog ensures that the Team and Product Owner have sufficientl
Should you have business as Product Owners? Is the Release Train Engineer a Delivery Manager? Where do Project Managers go? Aren’t Epic Owners the executive? Everyone gets these things wrong. Find out how to avoid SAFe’s implementation traps.
Are you still asking the ‘three questions’. It’s time you learned some better patterns to inspect your progress toward the team’s Sprint Goal.
When things get stale, ROTI is a simple pattern for team feedback that places the ownus of actions for improvement back on them.
What does a Scrum Master do all day? Run events and facilitate meetings? The Scrum Master role has evolved greatly over the last 20 years and now encompasses leadership, coaching, and growing agility through Scrum.
Copyright © Zen Ex Machina® and ™ (2021). All rights reserved. ABN 93 153 194 220