What is sprint planning?
Sprint planning comes from Scrum, the agile framework used widely in software development. Work is organized into sprints: fixed periods, usually one to four weeks long, at the end of which the team delivers something usable. Sprint planning is the meeting that starts each one. The team looks at the prioritized backlog of work, agrees a sprint goal, selects the items it can realistically complete and breaks them into tasks.
The key ideas are the fixed time box and the team's own commitment. Nobody hands the team a list; the team decides how much it can take on, based on what it actually finished in previous sprints.
Why it matters
Why sprint planning matters
It replaces the long plan that is wrong by week three with a short plan that is right for the next two weeks. For work where requirements change as you learn (websites, apps, ongoing social and performance campaigns), that is a better fit than a single upfront schedule. Each sprint ends with something to review, so the client sees progress early and the direction can change without throwing away months of work.
It also protects the team. A sprint, once planned, is meant to be stable; new requests go into the backlog for the next one rather than interrupting the current one.
In practice
How sprint planning works in practice
- 01
Before the meeting, the product owner (on agency projects often the account lead or producer, working with the client) orders the backlog by priority and makes sure the top items are clear enough to start. In the meeting, the team agrees the goal for the sprint in one sentence, then pulls items from the top of the backlog until its capacity is reached, using the pace of recent sprints as a guide.
- 02
Each item is broken into tasks with owners, and the meeting ends with a sprint backlog the team believes in. A two-week sprint rarely needs more than two hours of planning. Then the sprint runs, with a short daily check-in, and ends with a review of what was delivered and a retrospective on how the team worked.
At RIOT
Sprint planning at RIOT
Most of our work is production, built around fixed shoot days that do not sit neatly inside a sprint. Some of it does fit. A run of ads like the Meta ad engine we built for Homebase from February to April 2025, or the two months of social product films for Gantri, has the short, repeating rhythm that sprint planning was made for: plan a batch, make it, learn from it, plan the next.
Watch out
What people get wrong about sprint planning
Treating the sprint as a deadline to cram into. A sprint is a forecast based on real capacity; overfilling it guarantees spillover and erodes trust in the process. The second mistake is applying sprints to everything. A shoot with a fixed date, a crew and a location is a waterfall problem, and forcing it into two-week sprints adds meetings without adding clarity.
And skipping the goal. A sprint without a goal is just a to-do list with a deadline.
