A tiny guide to Sprint Planning in Scrum

  1. What can we do in this sprint?
  2. How are we going to do it?


  1. Sprint Planning shouldn’t be led by anyone besides the Development Team. Not the Scrum Master, not the Product Owner, not the PM. It’s harder for the Development Team to take ownership of their work if they aren’t leading the discussion.
  2. Sprint Planning shouldn’t gather a collection of unrelated tickets for the Sprint. As much as possible, tickets should all relate to the single Sprint Goal so that people can work together towards a single iteration.
  3. Sprints should never be pre-planned before Sprint Planning starts. The Sprint Backlog should be empty when Sprint Planning starts, so there’s no hidden pressure to commit to a pre-planned sprint. I’m talking to you, Product Owner who puts tickets into “sprint buckets” before Sprint Planning.





Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Should I go for microservices or a monolithic application?

Modern cloud virtualization

Languages I’ve Learned, or Not — Web 1.0

Postman: Introduction to Environments

Creating a CSV File from SQLAlchemy with Python!

How to open an existing .Net Core project Visual Studio Solution in Visual Studio Code (VSCODE)

What is Scrum?

Tatsu Patch Notes: 4th of Dec 2020

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Mike Crittenden

Mike Crittenden


More from Medium

Agile vs Waterfall: What is the Difference? Which Method is Best for You?

Scrum: Adaptive Software Development

A comprehensive list of benefits of using online project management

Woman sitting alone at an office computer desk.

What Are The Complete Scrum Artifacts?