Sprint Planning - Getting it done right
Outcome: Commitment to reach the Sprint Goal
Output: Sprint Goal and Sprint Backlog
Goal: Get the team ready to reach a meaningful goal by the end of the Sprint
How long | What | Who | How |
5’ | Set the Stage | Product Owner | Product Owner sets the stage by stating why the Sprint is important and what matters most for the business and customers right now |
15’ | Sprint Goal | Scrum Team | Product Owner shares a draft of the Sprint Goal based on why the Sprint matters and sharpen it with the whole team |
5’ | Sprint Name | Scrum Team | The Scrum Master or Product Owner asks the team to suggest on a name for the Sprint. This can be anything, a superhero, song, movie. The point is making it fun and engaging |
90’-120’ | Sprint Backlog | Developers | Based on the Sprint Goal, Developers create the Sprint Backlog. This is the moment to talk about how to get it done. Developers will talk in detail about their strategy to reach the Sprint Goal |
5’ | Start the Sprint | Scrum Team | As you have the Sprint Goal, Sprint Backlog, Sprint Name, and the commitment, start the Sprint |
Step by step to get to a successful Sprint Planning
Untrapping Product Teams
Supercharging your product knowledge to rock the world
Join 19K+ professionals to get weekly insights dpereira.substack.com