YDS: How Detailed of a Plan is Created in Sprint Planning?

Today's question is all about Sprint Planning! How deep of a plan do we need to get started with the work? Time to talk about emergence, complexity, and Product Management. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

How does your team handle Sprint Planning? Let us know in the comments!

This is one of those Scrum Master interview questions about Scrum that can throw you off. Do you understand how to facilitate a great Sprint Planning event? These Scrum Master day in the life questions can be tricky. Perhaps some Scrum Master training could help? Want to learn more about Scrum?

Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -

Join Ryan and Todd in a Professional Scrum Master course:

And make sure you subscribe to the channel!

DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week!

FTC DISCLAIMER: This video is not sponsored by anyone.

Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems.

#scrum #agile #professional scrum

[healthywithbenna]

You can't plan complexity perfectly, I love that. Thanks for another great episode guys 👌👌

[paulcasanova]

Great episode and great question!
I would say the experience of the team would be another factor to consider.
A while back I worked with a vendor provided team who were new to the organisation and therefore the product, and a new-to-the-role product owner, and found that encouraging the team to talk through their game plan for the sprint more deeply, helped to reduce friction and assumptions between them. Over several sprints they were then able to zoom out (or abstract) on their planning as they came to intuit how they worked together - their system I guess.
My current team have been together for 3 years. They know the work, and each other, so thoroughly, and they are so good at proactively refining together that sprint planning is almost not needed - I'm humbled!!

[sudakshinaghosh]

I need some guidance on a situation. There are some shy team members who do not open up that easily and because of that there are regular miscommunications and delays etc. There are also different personalities in the team . How to tackle this situation?

[roamingfreek]

Great video.. I just got out of a sprint planning meeting where the team spent over 40 minutes on one user story. How could I have avoided this.. by addressing this in the backlog refinement session ?

Thanks.

[kensaiyeahyeah]

I think the sprint goal should be referenced more. Something like "Enough so that the developers feel like the sprint goal can be met"?

[krod]

Question: What if the developers on the team are not technically capable to build an increment in the 1st Sprint. They need to learn/get training before they can have enough knowledge to complete an increment. So then would that still be considered a Sprint Goal to get training? It does not directly provide value to a customer with any increment.

[satisfiedornot]

Who solely owns the sprint planning ? Who facilitates it ?

[MrShairKhan]

1. We do PI planning based on the Objectives set by our PO and create a road map for next 5/6 sprints. Developers choose the work how it is done in each of the sprint.
2. During the Sprints our team do the refinements of PBI for the next sprint.
3. Since the refinement is already done in earlier sprint and team knows what the Sprint Objective or Goal looks like(already arrived during the PI) so the Sprint Planning is bit simplified and doesn’t take much time. Team simply Summarises what can be done in this sprint and how will the chosen work be done. Team Addresses any questions that PO has and complete the Sprint Planning. But If there is any changes in priority from PO other than what was planned in PI then yes our Team goes through those three questions - Why is this Spirit Valuable?, What can be done in this Sprint? How will the chosen work be done?
4. My Question here is, during the PI and Refinements the team knows what is being done for the Sprint, now during Sprint Planning should the Scrum still go through Why is this Sprint Valuable- question? If yes then Should this be from PO or from Development team?