3 Signs a Team Is Struggling with Sprint Planning & How to Fix It

Learn 3 hidden danger signs that sprint planning might not be going well for your team. Then, get Mike's advice on how to fix it.

00:00 Sprint Planning Is One of the Longest Scrum Meetings
00:16 Danger Sign #1 That Your Team Is Struggling with Sprint Planning
00:38 #2 Sign Your Team Isn't Doing Sprint Planning Well
01:05 #3 Sign Your Team Hates Sprint Planning
01:31 How to Stop Struggling With Sprint Planning
01:46 How Be Quick But Don't Hurry Applies to Sprint Planning
02:35 How Rough Estimates Help with Sprint Planning
04:04 When Too Much Thinking Is Too Much Thinking

[catheyboocat-design]

I have a brand new team trying to develop a brand new application and frankly planning meetings are more like refinement meetings. We have those almost daily at this time but when we go into planning it’s like they are reading this PBI for the first time. I know we will get better as we go but it is painful. Thank you so much for sharing your wisdom. I appreciate every video. Cathey

[AFCAT-dkpo]

Suppose in one team there are 5 people and it's a two week Sprint. So the estimated hours should be around 300 hours. 5 resource * 10 days * 6 hours.

[okwstoi]

Once you've identified a Scrum team's average capacity, how much would you recommend reducing it by to allow for unexpected scope in a sprint? Really enjoying these videos Mike - so clear 😊😊

[math]

Once an active sprint begins and new information becomes available can the story be updated during the active sprint to reflect the LOE required to complete the story?

[softwareminimalist]

Agree with everything but the "hour estimates". List of tasks, yes. Hour estimates = micromanagement.