Trello was not built for sprints. It was built for lists and cards. But thousands of teams run sprints on Trello because it is simple and their team already uses it. The gap: Trello has no velocity tracking, no capacity calculation, and no sprint reports. You need external tools to fill those gaps.
This guide shows how to pair the Sprint Velocity Calculator with Trello to plan sprints based on data, not guesswork.
Why Trello Teams Need Sprint Planning Tools
Without velocity data, sprint planning on Trello goes like this: the team looks at the backlog, drags cards into the sprint list until it "feels like enough," and hopes for the best. Some sprints finish early. Most finish late. Nobody knows why.
Velocity tracking fixes this. When you know your team completes an average of 25 story points per sprint, you stop loading 40 points of work.
Setting Up Sprints in Trello
Trello does not have sprint primitives. Build them with lists and Power-Ups.
Board structure: Create lists for "Backlog," "Sprint [Number]," "In Progress," "Review," and "Done." At the start of each sprint, create a new sprint list. At the end, archive it after recording velocity.
Story points: Use the Custom Fields Power-Up to add a number field called "Points" to every card. Or use the Scrum for Trello Power-Up, which adds points and burndown charts.
Sprint boundary: Pin a card at the top of each sprint list with the sprint goal, capacity, and dates. This is your sprint contract.
The Sprint Planning Workflow
Step 1: Calculate capacity. Use the Sprint Velocity Calculator. Enter your team size, sprint length, and historical velocity. Account for PTO, holidays, and on-call rotation. The calculator gives you a realistic capacity number.
Step 2: Prioritize the backlog. Score top backlog items using RICE or the value-effort matrix. Sorting by priority ensures you pull the highest-value cards first.
Step 3: Load the sprint. Drag cards from "Backlog" to the sprint list. Track the running point total using Custom Fields. Stop when you hit 80-85% of capacity. Leave buffer for surprises.
Step 4: Run the sprint. Move cards through "In Progress" and "Review" to "Done." Track progress daily with a quick standup. If the team is ahead, pull one more card. If behind, cut scope early.
Step 5: Record velocity. At sprint end, count the total points in "Done." Enter this in the Sprint Velocity Calculator to update your running average. Archive the sprint list.
Tracking Velocity Without Built-in Reports
Trello does not generate velocity charts. You need to track velocity manually or with tools.
Manual method: Create a "Velocity Log" card on your board. After each sprint, add a comment: "Sprint 14: 28 points planned, 24 completed." After 5 sprints, you have enough data for a reliable average.
Power-Up method: Corrello or Screenful add Trello reporting with velocity charts, burndown, and cycle time. These cost extra but save time for teams running serious sprints.
Calculator method: Use the Sprint Velocity Calculator to track velocity and model future sprints. Enter historical data and get projections for upcoming sprints.
Tips for Trello Sprint Teams
Use Trello's calendar Power-Up to set due dates on sprint cards. Sort the sprint list by due date so the team sees what needs to finish first within the sprint.
Create a "Sprint Retro" card template with sections: What went well, what did not, action items. Copy this card at the end of each sprint. Attach it to the archived sprint list for reference.
For teams managing multiple Trello boards across squads, standardize your story point scale. A "3" should mean the same thing on every board. The feature prioritization guide covers standardization across teams.
Archive completed sprint lists instead of deleting them. This creates a visual history of your team's output. Scroll left to see 20 sprints of archived work. It is a quick health check for delivery consistency.