Agenda · Planning
Scrum Guide sprint planning for a two-week Sprint: agree why, pick what fits real capacity, plan how, then check confidence.
Opens in the builder. No sign-up to try it; free forever to run it live.
By the end of this meeting: The team has a clear Sprint Goal and a Sprint Backlog it believes it can finish.
01Inside
5 blocks in 120 minutes, in order, with the facilitator's tips.
02Why it works
20 minutes of open floor with a countdown everyone can see, and a talk-balance meter so the loudest voice doesn't take all of it.
Capture the decision and its owner with one click while it's said. It lands in the summary, word for word.
Everyone types at once and ideas land on the shared screen together. The quiet person's idea gets the same space as everyone else's.
One tap each on a phone, live bars on the screen. A tick shows who has voted, never what they chose.
Decisions and actions are read back, the summary is already written, and a finish on time earns the confetti.
03In the room
The shared screen, every phone and the summary afterwards, drawn from this agenda.
On the shared screen
Each block runs on its own timer on the shared screen, and the video call changes with each block, so the meeting keeps to time.
On every phone
People scan the code or tap their invite and answer in the phone's browser. No app to install, no account to make.
Afterwards
Decisions and actions are captured as they're said. When the meeting ends, everyone gets the summary, and one link shares it.
04How to run it
Refine the backlog before the meeting; if planning keeps running long, the cause is usually poor refinement or oversized items.
Start with why: draft a Sprint Goal the whole team can repeat, not a vague list of tickets.
Let the Developers pull items based on their real capacity and resist stakeholder pressure to overcommit.
Break the first items into a plan, but don't try to list every task upfront.
Close with a fist-of-five confidence vote, then confirm the Sprint Goal and Sprint Backlog.
05Questions
Still deciding?
Run your next meeting on it. Every new account gets Pro free for 14 days, no card.
The Scrum Guide caps it at eight hours for a one-month Sprint. Experienced teams often need 90 to 120 minutes for a two-week Sprint.
Why the Sprint is valuable (the Sprint Goal), what can be Done this Sprint, and how the chosen work will get done.
The whole Scrum Team: the Product Owner brings the backlog and input on the Sprint Goal, the Developers choose and size the work, and the Scrum Master facilitates.
Usually because refinement was poor or items are too big, which pushes detailed discussion into the planning meeting.
The structure, timings and tips on this page come from these sources.
Keep going
Open it in the builder, adjust the minutes, press Run live. Everyone joins with a scan.
Free forever · Pro free for 14 days · No card needed · Guests never sign up
Sprint planning meeting120 minutes · Free template