Team Capacity Planning Without a Spreadsheet
Team Capacity Planning Without a Spreadsheet
TLDR: Visual capacity planning on your Kanban board replaces error-prone spreadsheets with real-time workload awareness that the whole team can see and adjust.
Capacity planning usually means opening a spreadsheet, listing team members, subtracting vacation days and meetings, calculating available hours, and mapping those hours to tasks. The spreadsheet is outdated the moment someone calls in sick or a meeting gets added. There is a simpler approach that uses your existing project board and stays current without manual updates.
Why Spreadsheet Capacity Planning Fails
Spreadsheets fail at capacity planning for three reasons. First, they are static. The moment you finish updating the spreadsheet, the inputs have changed. Someone's estimate was off, a task took longer, a new priority emerged. Second, they are invisible. The spreadsheet lives in someone's drive, and the team does not reference it during actual work. Third, they encourage false precision. Calculating that a developer has exactly 31.5 available hours this sprint implies a level of accuracy that does not exist.
Teams spend hours maintaining capacity spreadsheets that no one looks at during the sprint. The investment produces a planning artifact, not a planning practice.
Visual Capacity on Your Board
Your project board already contains the information you need for capacity planning. You just need to read it differently.
In LocalPM, every card assigned to a team member represents a claim on their capacity. The number of cards assigned to someone in the In Progress and To Do columns shows their current workload at a glance. No spreadsheet required.
Set a simple rule: no team member should have more than three cards assigned in the active sprint at any time. When someone finishes a card and moves it to Done, they pull the next card from the sprint backlog. This pull-based system naturally balances workload without centralized planning.
The WIP Limit Approach to Capacity
Work-in-progress limits are the simplest form of capacity planning. Instead of calculating hours and mapping them to tasks, you set a maximum number of items that can be in progress at any time.
For a team of four, a WIP limit of six for the In Progress column means the team is always working on a manageable amount of work. If all six slots are full and someone finishes a task, they pull a new one. If all six slots are full and no one is finishing, the team swarms to help complete an existing item rather than starting something new.
WIP limits handle vacations and sick days automatically. If someone is out, their in-progress items either get reassigned or the effective WIP limit drops. Either way, the board reflects reality without anyone updating a spreadsheet.
Accounting for Meetings and Non-Sprint Work
The hidden capacity killer is time spent in meetings, on support tickets, and on other work that does not appear on the sprint board. A developer who is in meetings for fifteen hours a week has dramatically less sprint capacity than one with five hours of meetings.
Instead of tracking meeting hours in a spreadsheet, account for them in your sprint commitment. If your team typically completes twenty story points per sprint but one member has a conference week, reduce your sprint commitment to sixteen or seventeen. Use your historical velocity to calibrate rather than trying to calculate exact available hours.
In LocalPM, you can note known capacity reductions directly in the sprint description. "Sprint capacity reduced: Alex at conference Monday through Wednesday" gives the team context without requiring a separate planning document.
The Monday Morning Capacity Check
Replace your spreadsheet with a two-minute Monday morning capacity check during standup. Each team member answers one question: "How available are you this week on a scale of one to five?" A five means fully available. A three means significant meetings or other commitments. A one means barely available.
Multiply the team's total availability score by your average points per availability unit from previous sprints. This rough calculation is faster, more honest, and more accurate than a detailed spreadsheet because it captures real-world availability rather than theoretical hours.
When You Do Need More Detail
Some situations require more detailed capacity planning. Resource-constrained projects with hard deadlines, teams with highly specialized roles where work cannot be redistributed, and portfolio-level planning across multiple teams all benefit from more structured approaches.
Even in these cases, start with visual board-level capacity and add detail only where it is needed. A hybrid approach where the board handles daily capacity management and a quarterly plan handles strategic allocation gives you the best of both worlds without the overhead of maintaining a detailed spreadsheet every sprint.
Your team's capacity is visible on your board right now. The number of assigned cards, the WIP limits, the flow of work from left to right. Learn to read these signals and you will plan capacity more accurately than any spreadsheet ever could. For the next level, explore assigning work based on skill rather than just availability, and use team avatar colors to make workload distribution visible at a glance.
Learn More
Ready to ditch the spreadsheet and plan capacity visually? Check out the complete training series:
Watch the Project Management AI Playlist on YouTube
For more project management insights and resources, visit subthesis.com