How to Plan Your First Sprint in One Afternoon
You don't need training, a certification or a week of setup to run your first sprint. You need a list of work, an honest guess at how much you can finish, and an afternoon. Here's the process, in order.
Step 1: Dump everything into tickets (30 minutes)
Get every open piece of work out of heads, chats and spreadsheets and into one place, one ticket each. Don't organise yet. Ask each person what they're working on and what they're worried about forgetting. If it's not written down, it isn't going to be planned.
Step 2: Decide what matters this cycle (20 minutes)
Now sort. For each ticket, ask "if we only did five things this fortnight, would this be one?" Anything that isn't urgent, or is blocked, or is vaguely "someday", goes in the backlog. Parking work isn't failing — it's deciding.
Step 3: Pick a length
One or two weeks suits most small teams. If you're unsure, take two weeks: it's long enough to finish something meaningful. In Alignr the planned end date defaults to two weeks after you start, and it's a target rather than a hard stop, so you can close the sprint earlier if a shorter cycle suits you.
Step 4: Choose a realistic amount (20 minutes)
This is the step that trips up new teams: planning for a perfect fortnight. Instead:
- Count working days after leave, holidays and known client meetings.
- Leave a little slack for the unexpected — something always turns up.
- If your first guess feels ambitious, remove one ticket.
You'll get better estimates after two or three sprints. The first is partly an experiment.
Step 5: Give every ticket one owner (10 minutes)
One person, one ticket. Shared ownership usually means nobody feels responsible. If a job needs two people, split it into two tickets or add a checklist.
Step 6: Break big tickets down (20 minutes)
Any ticket you can't finish in a few days is too big. Split it, or use a checklist inside the ticket so progress shows up as boxes get ticked. Watch for dependencies too — if one ticket can't start until another finishes, mark it, so the blocker is visible before it bites.
Step 7: Start the sprint and put the review in the calendar (10 minutes)
In Alignr you start a sprint for your team, then add tickets to it from any of the team's boards. Tickets already in progress join automatically. Then do the most important thing of all: schedule the end-of-sprint review now. If it isn't booked, it won't happen.
A sprint isn't a promise to finish everything. It's a promise to look honestly at what you did and didn't.
During the sprint
- Move tickets as you work, not in a batch on Friday.
- Add new requests to the backlog rather than the sprint, unless something truly displaces another item.
- Use a short daily update if it helps — a written standup works well for distributed teams.
At the end
Close the sprint. Finished tickets move to your Finished board, and when you start the next sprint, anything unfinished carries over. Then run a short retro: what went well, what got in the way, what will we change. Retros and analytics are available on the Team plan ($2 per user per month, USD); until then a shared note does the job. Our async retro guide shows a lightweight format.
What "good" looks like after three sprints
- You finish roughly what you plan, and you know why when you don't.
- Nobody asks "what are we working on?" in the group chat.
- Each retro has produced a small change you can actually name.
Sprint boards work on the free plan, so you can run this whole afternoon for nothing. If you're unsure how sprints differ from a plain board, read Trello boards vs sprint boards. Otherwise, start free and plan your first cycle today.