How to run sprint planning with a remote team
Sprint planning is the session where a team decides what it will finish in the next sprint and why. In an office it was a room, a board, and an afternoon. On a remote team it is usually a long video call where half the time goes to reading tickets aloud.
Most of that reading can happen before the call. Do the prep in writing, use the live time for the few choices that need a conversation, and leave the plan in the channel where the work will happen.
The usual way
Remote sprint planning tends to look like this.
- A two-hour call. Everyone joins at once, and someone screen-shares the backlog from the top.
- Estimating from cold. People see a ticket for the first time on the call and guess at its size.
- Capacity by memory. Halfway through, someone remembers a teammate is out on Thursday.
- A plan that lives in the tracker. The sprint is "committed" in a board most of the team opens once a week.
The call ends with a full sprint and a tired team. By the second day, people are asking in DMs what the goal was.
A sprint planning routine that works remotely
1. Groom the backlog in writing, a day ahead
The day before planning, the person who owns the backlog posts a thread in the team channel: the candidate items, ranked, each with a one-line summary and a link to the ticket. Teammates reply with questions, concerns, or rough sizes when they have a minute. Teammates in other time zones get the same say as everyone else.
Anything that needs a design answer gets flagged in the thread now, not discovered on the call.
2. Post capacity before anyone estimates
In the same thread, each person posts what they have for the sprint: days out, on-call shifts, and anything already promised to another team. A short list is enough. Planning against the real number of working days beats planning against an ideal one.
3. Agree on one sprint goal
Start the live part with the goal, not the tickets. One sentence that says what will be true at the end of the sprint, such as "New customers can import contacts from a CSV." Then pick the backlog items that serve it. Items that do not serve the goal wait for the next sprint unless there is a clear reason.
4. Keep the live part short
With the reading done in the thread, the live conversation covers only what needs talking through: the goal, the items with open questions, and anything that does not fit in the capacity. Thirty to forty-five minutes usually covers it. Audio is enough; cameras are optional.
5. Give every item one owner
An item with two owners tends to have none. Each item in the sprint gets one name. Others can help, but one person answers for it.
6. Post the plan where the work happens
End by posting the sprint in the team channel: the goal, the items with their owners, and the date of the review. Pin it. When someone asks what the sprint is for, the answer is one click away. Decisions made during planning go there too; how to keep a decision log in team chat covers the format.
A short planning checklist
- Backlog thread posted a day ahead, ranked, with links
- Capacity posted by each person before estimating
- One-sentence sprint goal agreed first
- One owner per item
- Plan posted and pinned in the team channel, with the review date
How Bullpen fits
Bullpen is team chat with walk-in voice rooms and AI helpers on the roster, so sprint planning can live in the team's own channel from prep to plan.
The prep happens in a thread. The backlog and capacity posts sit with the team's day-to-day messages, so anyone can read them before the live part.
The talk happens in the channel's walk-in voice room. The room is already open beside the channel, so there is no link to send. People step in when planning starts and step out when it ends. Someone who only needs to weigh in on one item can walk in for that part.
Wren writes the notes. In a channel's walk-in voice room, Wren posts notes and action items back to that channel, so the goal and the owners agreed out loud end up next to the written prep. More on that in recaps that land in the channel.
Nix keeps the dates. When an owner says a piece will be ready for review by Wednesday, mention Nix in that thread and the reminder arrives in the channel on the day. How to keep track of follow-ups in team chat covers the details.
Scout remembers last sprint. Mention Scout in the channel and ask what the team committed to last sprint, or why an item was pushed. Scout answers from what was actually said and links the message it came from.
When the sprint ends, how to run a remote retrospective picks up in the same channel.
Try it at your next planning
Post the ranked backlog and a capacity prompt in your team channel the day before planning, and open the live part with a one-sentence sprint goal.
Start free and plan your next sprint in the channel where the work already lives.