Build a sprint planning facilitator agenda

Sprint Planning Should Run in 45 Minutes

Sprint planning that runs 90+ minutes is a signal of poor backlog hygiene — the team is grooming in the wrong meeting. Atlassian's sprint planning guide and Scrum.org's framework both recommend separating grooming from planning: a pre-groomed backlog makes planning a commitment meeting, not a discovery meeting. Linear's method goes further: if an item takes more than 10 minutes to discuss in planning, defer it and keep the team moving.

How the Build a sprint planning facilitator agenda Prompt Works

The prompt enforces a 45-minute structure: 5-minute context, 15 minutes on top three items, 10 minutes on remaining capacity, 10-minute commitment check, 5-minute close. The commitment check step is the load-bearing ritual — "no commitments by silence" surfaces hesitations that would otherwise reveal themselves as sprint failures.

When to Use It

• Planning routinely runs >60 minutes.
• Sprints regularly miss their goals with no clear cause.
• A new EM or PM wants to reset the planning cadence.
• Engineers complain that items land in the sprint without discussion.
• Buffer capacity does not exist and the team is chronically overcommitted.

Common Pitfalls

• Grooming in planning. Grooming and planning are different meetings. Conflating them turns planning into a backlog-editing session.
• Silent commitment. If engineers don't explicitly commit, the sprint will miss quietly.
• No buffer capacity. 100% allocation guarantees spillover. Reserve 15-20% for surprise work.

Sources

• Sprint Planning — Atlassian
• What is Scrum? — Scrum.org
• The Linear Method — Linear
• Embracing Agile — Harvard Business Review