Keep Sprint Planning Short and Effective

Does your team complain that sprint planning takes too long? Maybe it does!

Does your team complain that sprint planning is a waste of time? Maybe your sprint planning isn't long enough.

Discover how to keep sprint planning short, but not too short.

00:00 Stop struggling with sprint planning
00:30 Be quick but don't hurry
00:40 The right length for sprint planning
00:52 When sprint planning is too painful

[webscenes]

Shift left:

For stories that are likely to be developed in the next 1 to 2 Sprints, we try to do as much preparation as possible before Sprint Planning in our Backlog Refinements.

For example, clarifying requirements and dependencies, estimating and, if necessary, splitting stories into pieces that can be done in one Sprint.

[rajeswarikv]

HI Mike, i read your article on Capacity we will do based on available productive hours. Either capacity or velocity, we will estimate a single PBI . IN commitment based during sanity check, why are we calculating total time of the team (available) and comparing planned vs average velocity, as there is no relation between time and velocity in SP's. Not able to post in the blog section and hence posting here. Kindly clarify on this