Sprint planning doesn't need to happen in a separate tool. With Figma's flexible canvas and real-time collaboration features, you can organize sprints, track work, and keep your team aligned in the same design platform where much of your work already lives. This guide shows you how to set up and execute sprint planning directly in Figma.
Why Figma
Figma's strength lies in its real-time collaboration and visual organization. Unlike spreadsheets that require constant switching between tools, or heavy project management software that demands significant setup, Figma lets you see your entire sprint at a glance. You can drag tasks around, resize cards, color-code by status, and have your whole team viewing and editing the same board simultaneously. Since most product teams already have Figma open, sprint planning becomes part of your existing workflow rather than another tab to manage.
Additionally, Figma's commenting and @mention features keep context close to each task. You don't lose discussion threads in Slack or email. Team members can update task status, ask questions, and reference specific areas of your sprint plan without context switching. For teams that work heavily with design, this integration is particularly valuable since your sprint board lives alongside your design files.
Step-by-Step Guide
1. Create a New File for Your Sprint
Start by opening Figma and creating a new file. Click the "New file" button from your dashboard, or use File menu > New. Name it clearly with your sprint identifier, like "Sprint 24 - Planning Board" or "Q2 Sprint 3 Planning."
Once the file is created, set up your basic structure. You'll want a clean canvas that accommodates multiple sections. Create frames for each major category you'll need. At minimum, set up frames for: Backlog, In Sprint, In Progress, Review, and Done. These will serve as your swim lanes.
Use the rectangle tool to create a large frame (2400 x 1800px is a good starting size). Title this "Sprint Board." Inside this frame, create five equal columns using the frame tool. Label each column with a text box at the top: "Backlog", "Sprint Selection", "In Progress", "In Review", "Completed". Use consistent styling, like a 32px header text in your brand color.
2. Set Up Task Card Components
Create a reusable task card component that you'll use throughout your sprint. This ensures consistency and makes updates easier. Click Assets panel on the right, then create a new component. Make it 280px wide by 180px tall.
Inside this component, add several layers. Start with a rectangle for the background (light gray, #F5F5F5). Add a 1px stroke in #E0E0E0. Below that, create a text layer for the task title (14px, bold, dark gray). Add another text layer for story points (12px, right-aligned). Create a small circle for priority indicator (use a component for this too). Add a final text layer for the assignee name (11px, italic, medium gray).
Save this component with a clear name: "Task Card". You can now drag multiple instances of this component into your columns. Each instance can be edited independently while maintaining the overall design structure.
3. Populate Your Backlog and Sprint Items
Before the meeting, populate your backlog items in the leftmost "Backlog" column. Use your existing backlog from your product management system or tool. For each item, drag an instance of your Task Card component and update the text layers with the task name, story points, and priority level.
Add 15-20 items to your backlog. Color-code by priority: red circles for critical, orange for high, yellow for medium, gray for low. This visual distinction helps your team quickly understand relative importance without reading every card.
For your sprint scope (determined in a pre-planning session), move identified items to the "Sprint Selection" column. Don't move everything at once. Instead, do this collaboratively during the actual planning meeting so the team can discuss and decide which items to commit to.
4. Establish Team Capacity on the Board
Create a dedicated section for capacity planning. Below your main sprint board, create a table-like structure to track capacity. Use rectangles and text boxes to build a simple layout with columns for: Team Member, Capacity (hours), Allocated (hours), and Available (hours).
Add each team member as a row. If using story points, create a similar table with "Team Member", "Total Capacity (SP)", "Allocated (SP)", and "Remaining (SP)". For story points, you can use the tool to help pre-calculate team velocity, then update your Figma board with those numbers.
Update these numbers manually as you move tasks into the sprint. As you assign tasks, subtract story points from the Available column. This gives real-time visibility into whether you're overbooking your team. You can also add a text layer that shows total sprint capacity in large numbers, updated throughout planning.
5. Run Live Planning and Move Cards
During your sprint planning meeting, share your Figma file and ensure everyone has edit access. Open the file in a larger window or projected view. As your team discusses which backlog items to commit to, have someone (typically the product manager or Scrum master) drag cards from "Backlog" to "Sprint Selection."
Use the move tool to drag cards. Create a visual "staging area" where cards that are being discussed sit before they're formally committed. This prevents accidental moves and gives everyone time to see what's being considered. Once the team agrees, move the card into the Sprint Selection area.
As you move cards, update the capacity table in real-time. Click on the Available column for each assignee and update the number. If someone is at 0 available capacity, highlight that row with a warning color (light red, #FFE6E6) so the team knows not to assign more work to them.
6. Assign Tasks and Set Priorities
Once items are committed to the sprint, assign them to team members. Click each task card and update the assignee text layer with the person's name. You can also add small avatar placeholder circles if you want visual indicators, or use color coding for assignees.
Set clear priorities within the sprint. Even though all sprint items are committed, some have higher priority. Add a number prefix to task titles (1., 2., 3., etc.) or use different colored priority circles. This helps your team know which to tackle first if they finish early or if scope suddenly changes.
Create an ordering within each column. In the "In Progress" column, put the highest-priority items at the top. As work moves through columns, the natural top-to-bottom reading order should reflect priority and work sequence.
7. Enable Real-Time Status Updates
During the sprint, team members update task cards as they work. Move cards horizontally across columns: Backlog -> Sprint Selection -> In Progress -> In Review -> Completed. This physical movement creates a satisfying visual of progress.
Encourage team members to update the task card text if scope changes. Click into any card and edit the title or add context. Use the comment feature (press C on any selection) to add quick notes, blockers, or questions. These comments are visible to the whole team and create an audit trail of decisions.
Set a daily ritual where the team spends 2 minutes scanning the board before standup. This often replaces part of standup since the visual board communicates status more efficiently than verbal updates.
8. Run Sprint Reviews and Retrospectives
At sprint end, archive completed items. Create a new frame below your main board called "Sprint 24 Completed Items". Move or copy all cards from the "Completed" column here. This creates a historical record of what you shipped.
Use Figma's share feature to generate a summary snapshot. Take a screenshot of the completed board and share it with stakeholders. This visual summary communicates team output better than a list.
For retrospectives, create a new section on the same file with three columns: "What Went Well", "What Could Improve", and "Action Items". Team members can add text or comment to each area. Keep this visible for future reference so you can track patterns across sprints.
Pro Tips
- Use Figma's color library for consistent status colors across sprints. Create a shared color style for "Sprint Committed" (green), "In Progress" (blue), "Blocked" (red), and "Completed" (gray).
- Set up a template file before each sprint. Duplicate your sprint structure each planning session so you don't rebuild the board from scratch. Reference your guide for planning best practices to inform your template structure.
- Pin your sprint board file to your Figma dashboard so it's the first thing your team sees when they open the app. This increases visibility and adoption.
- Use Figma's multiplayer cursors to see who is editing which card in real-time. This prevents duplicate edits and shows who's actively engaged in planning.
- Export capacity reports as images and share in Slack or your status updates. Figma's export feature makes this quick and professional.
When to Upgrade to a Dedicated Tool
While Figma works well for sprint planning, consider moving to a dedicated tool if your team regularly struggles with certain limitations. If you need automated burndown charts, historical velocity tracking across 20+ sprints, or integration with development tools like GitHub and Jira, tools built specifically for sprint management may serve you better.
Also consider upgrading if your sprints consistently involve more than 50 items or your team exceeds 12 people. Figma's canvas, while flexible, can feel cluttered at that scale. You might explore the PM tools directory for alternatives, or review our comparison between design tools and their planning capabilities.
If you need to track work across multiple teams with different sprint cycles, or if leadership requires complex burndown analytics, a dedicated solution like Jira, Azure DevOps, or Linear becomes more practical. That said, you can keep your visual sprint board in Figma while using another tool as your source of truth, updating Figma weekly for visibility.