We’ve all been there: The two-hour sprint planning meeting that feels like it’s going in circles. The team is disengaged, stakeholders are hovering, and by the end of it, nobody is actually sure what the top priority is.
Sprint planning shouldn’t be a bureaucratic hurdle; it’s the heartbeat of your sprint. If it feels like a waste of time, you’re likely focusing on the wrong things. Instead of obsessing over every Jira ticket, structure your meeting around these three questions to regain focus.
1. What is the one thing we must achieve?
Teams often enter planning with a "fill the bucket" mentality—how much work can we cram into these two weeks? This leads to fragmented focus.
Instead, start by defining a single, clear Sprint Goal. If everything else was stripped away, what is the one outcome that makes this sprint a success? By anchoring the planning around this, you empower the team to say "no" to secondary tasks that don't contribute to the primary goal.
2. What is standing in our way right now?
Agile isn't about ignoring reality; it’s about acknowledging it early. Don't wait for the daily stand-up to uncover blockers.
Ask the team specifically about dependencies, technical unknowns, or missing information. If a task has an "I think" attached to it, flag it. Frame these unknowns as "questions to be answered" during the sprint, but ensure you’ve allocated capacity to resolve them. Ignoring a technical risk because it’s "too big for planning" is a recipe for a failed sprint.
3. Does this plan actually reflect our capacity?
We’re all optimists when we’re planning two weeks out. We assume 100% productivity, ignoring meetings, holidays, and the inevitable "quick questions" that derail our developers.
Be honest about your team’s real velocity. If you’re constantly missing your sprint commitments, stop changing your team's output and start adjusting your input. Planning for 80% capacity is not an admission of defeat; it’s a strategy for consistency.
Takeaways
- Start with the Goal: Define the single most important outcome before looking at any tasks.
- Surface Risks Early: Don't hide unknowns; identify and plan to resolve them as part of the sprint.
- Plan for Reality: Always account for non-development time; aim for consistent delivery over aggressive commitment.
Resources
Modern Project Management for Distributed Teams
PM Squared shares practical tools, templates, and lessons for PMs navigating remote work in 2026.
Browse Resources →