Virtual Sprint Planning

Virtual sprint planning on a video call usually goes one of two ways. Either the product owner talks for an hour while engineers sit on mute, or everyone estimates by typing a number into a chat and hoping for the best. The real discussions — "What are the technical unknowns?" "Have we built something like this before?" — never happen because there's no space for them.

On Flat.social, sprint planning splits into the conversations that actually produce good estimates. The product owner presents stories in the Conference room stage, then engineers break into small estimation zones — audio isolation rooms with whiteboards. Groups of 3-4 sketch architectures, map data flows, and debate complexity through spatial audio. The whiteboard catches risks that verbal discussion misses.

After estimation, the team reconvenes to reconcile differences and commit to the sprint goal. Discrepancies between groups spark the most valuable discussions. The sprint board lives on a billboard that everyone can see updating in real time. Planning becomes a working session, not a meeting.

Tips for Scrum Masters

Running sprint planning that produces real commitment:

1. Time-box the backlog presentation. Give the product owner 2-3 minutes per story in the Conference room. If a story needs more explanation, it's not ready for planning. Move it back to refinement.

2. Split estimation groups intentionally. Mix senior and junior engineers in each zone. The junior engineers ask clarifying questions that reveal hidden complexity. The senior engineers share context that improves estimates.

3. Use whiteboards for every story. Even simple stories benefit from a quick architecture sketch. Make it a habit. Groups that draw their approach on the whiteboard catch risks that verbal discussion misses.

4. Let discrepancies drive discussion. When groups reconvene with different estimates, don't average them. Ask each group to explain their reasoning. The gap between a 3 and an 8 is where the best engineering conversations happen.

5. Update the sprint board billboard live. As stories are estimated and committed, update the billboard in real time. Watching the sprint take shape creates shared ownership of the commitment.

Tips for Engineers

Making your estimates count:

Sketch before you estimate. Grab the whiteboard in your estimation zone and draw the data flow or component diagram. Visual planning reveals dependencies and edge cases that feel obvious only after you've drawn them.

Speak up about unknowns. If you don't understand a story, say so. "I don't know how the auth layer works here" is more valuable than a guess. Unknowns should increase the estimate, not get ignored.

Walk up to the product owner. If your estimation group has a question, don't wait for the reconciliation round. Walk over on the spatial floor and ask through proximity audio. Quick clarifications save time.

Pick up stories you estimated. You understand them best. Volunteer for the work your group discussed on the whiteboard. The context you built during estimation makes the sprint start faster.