Reconsider Sprint Planning Duration

If, possibly as a result of the Sprint Retrospective, you are considering changing the length of a sprint, this decision needs to happen as the first decision in the Sprint Planning Meeting.
Longer durations have lower overhead and allow some developers to focus better, while shorter durations allow for quicker course corrections.
Try to stay between 2 weeks and 1 month as a Sprint duration.

Review Product Backlog in Advance

The product backlog can be quite large.
Distill the backlog to a managable list of recommendations, and ensure the team sees the list ahead of the Sprint Planning Meeting.

Questions

Consider these 3 questions:
Why are we doing this Sprint?
What do we need to do to achieve that?
How much work can we complete?

Flow

Consider the flow of the upcoming Sprint

Focus

Keep in mind that a sprint works best if it is themed, allows the entire team to focus on the Sprint goals, and is not a random collection of high-priority features.


Read the original list of sprint planning rules here