Getting the Sprint Planning Done Right

Simplifying how you plan your Sprints

Originally published in GoRetro

Depending on how you handle your Sprint Plannings, that can be a blessing or a curse. The Scrum team may leave the room empowered or trapped, motivated or demotivated, inspired or pressured.

What’s your experience with Sprint Planning? Have you ever stumbled upon any of the following?

• Every Sprint is the same, more features, more output, and no clear goal
• Product Owners pressure the team to commit to output and forget the why
• Scrum Masters focus on velocity increasing and don’t challenge Product Owners or Developers
• Developers despise planning because they believe it gets in the way of getting their job done

If any of the above speaks to you, welcome to the club. You’re not alone.

Many teams struggle with Sprint Plannings, and as a result, Sprints become a trap and don’t help teams unleash their best.

Let me help you understand the critical aspects of valuable Sprint Planning.

Photo by Matt Noble on Unsplash

Understanding the Sprint Planning