How to Improve Sprint Planning Without Adding Another Meeting
If planning calls stall on missing information, prepare backlog context, goals, and estimates before the meeting. Use asynchronous discussion where practical, then bring the team together for decisions that need it. Review whether the preparation helps rather than adding another call.
By The Quely Team, Quely editorial team
Published . Last updated .
How can you improve sprint planning without adding another meeting?
The sprint planning call can stall when people first see an unclear backlog item in the meeting. A missing requirement or dependency then needs another conversation before the team can make a plan.
So what if you could improve sprint planning… without scheduling yet another call?
This post explains asynchronous sprint planning, how to prepare it, and how tools such as Quely can keep work and its context together.
The Problem with Traditional Sprint Planning
When a planning event tries to clarify the backlog, estimate work, and agree a goal at once, people may have too little time for each decision. Move useful preparation earlier and use the event to create the plan together.
Examples of questions to check with the team:
"Why is this taking 2 hours?"
"We’re just rehashing what’s already in Jira."
"Half the team isn’t engaged."
Remote and distributed teams feel this even more acutely. Coordinating across time zones adds friction, and lengthy video calls rarely match the deep focus time developers need to think through their work.
So the question becomes: how do you keep the intent of sprint planning, while removing the inefficiencies?
The Case for Asynchronous Sprint Planning
Asynchronous preparation lets people review work, ask questions, and contribute estimates before the team finalizes a plan. If you use Scrum, retain Sprint Planning: the Scrum Guide defines it as a collaborative event for the whole Scrum Team. Written preparation supports that event; it does not remove it.
Benefits to check in a trial:
Time zone friendly: Everyone can contribute during their work hours.
Encourages thoughtfulness: People can review work items and ask questions without pressure.
Fewer interruptions: Agree review windows, then compare interruption levels with the current process.
Documented by default: Keep estimates, questions, and decisions with the relevant work. Name who records the final agreement.
Think of it less like skipping a meeting and more like redesigning the process around flexibility and clarity.
How to Run Asynchronous Sprint Planning
1. Prep the Board
Start with a well-groomed backlog. The Product Owner role should:
Organize upcoming issues or user stories
Write clear acceptance criteria
Group them by priority or theme
Use tags or swimlanes in your planning tool to help the team navigate faster.
2. Share Context and Goals
Set the tone and direction for the sprint asynchronously:
Record a short Loom or write a summary of sprint goals
Link to key documents (customer feedback, roadmap changes)
Explain priorities and dependencies
This gives everyone the background they need without a long kickoff call.
3. Estimate Together, Asynchronously
Invite the team to review and estimate. Choose a tool with a documented async workflow, such as Async Poker for Jira. Check these requirements in a trial:
Hidden voting (to avoid bias)
Revealing story point estimates at once
Comment threads for clarification
Encourage developers to add comments or tag teammates when more info is needed.
4. Final Sprint Assembly
Once estimates and comments are in:
The team lead or scrum master reviews for alignment
Flag blockers or unestimated work
Make adjustments based on capacity
The Scrum Team then agrees the Sprint Goal, selected work, and plan during Sprint Planning. For another delivery method, agree a review process that gives everyone a chance to raise a material concern. Do not use an arbitrary meeting length to force an unresolved commitment.
Best Practices for Effective Async Planning
Set a deadline: Agree a review window that fits working hours and time zones. For example, allow one or two working days, then check whether the window is sufficient.
Standardize templates: Use consistent formats for user stories and estimation questions.
Make it visible: Use shared dashboards or workspace comments to keep track of progress.
Be inclusive: Encourage quieter team members to contribute in writing. It can lead to more balanced input.
Review retrospectively: After the sprint, review how well the async process worked. Tweak as needed.
Tools to Power Async Sprint Planning
If you're making the leap to async planning, the right tools matter. Here are a few worth exploring:
Quely: Bring work into a Space. Discuss and estimate with your team. Ask Orbit about the available context. Use Lenses to view decisions or open questions.
Jira + Confluence: Standard tooling many teams already use, with good support for comments and backlog grooming.
Async Poker: Check the Jira app’s current async workflow and plan terms. Planning poker is a method, so name and verify the product you choose.
Linear: Cycles provides recurring issue planning. Confirm which preparation, estimation, and review steps your team will use.
👉 We’ve written about tools that replace status meetings. Check them out for a deeper dive.
But What About Team Cohesion?
One concern with removing meetings is the potential loss of human connection. But async planning doesn’t mean zero interaction. It just shifts when and how those interactions happen.
You can still:
Leave video updates or voice notes to add tone
Use chats to celebrate good questions or clarify intent
Add a brief weekly check-in (if truly needed) to anchor the team
The key is to be deliberate: meetings should serve a purpose, not just a tradition.
Conclusion
Start the next sprint with reviewed work, explicit questions, and a clear goal. Trial asynchronous preparation and check whether it improves participation and the plan the team can explain.
Quely keeps work and its relevant context together. The team can discuss and estimate in a Space, then ask Orbit questions about the available material.
Keep a live discussion for the decisions that require it. Review the preparation process after the sprint and change what did not help.
Preparation is easier to review when people can trace a question to the work and the earlier discussion. See a worked example with a Jira item, a Slack discussion, and meeting context.
Find more Quely articles
Choose Quely as a preferred source in Google Search.
Prefer Quely on Google