The Spreadsheet Is Always Wrong
Every organization has a resource planning spreadsheet. It’s maintained by a project manager or team lead. It maps people to projects, weeks to capacity, and assumptions to color-coded cells. And it’s always at least partially wrong, because people’s actual allocation never matches the plan — meetings run over, incidents happen, tasks take longer than estimated, and priorities shift faster than the spreadsheet updates.
The spreadsheet isn’t wrong because the PM isn’t diligent. It’s wrong because planning human capacity at a granular level is fundamentally unreliable. People are not fungible units of output.
What Resource Planning Should Actually Do
Instead of trying to schedule human hours precisely, resource planning should answer three questions:
1. Do we have enough people for the work we’re planning?
This is a rough capacity check, not an hour-by-hour schedule. If you’re planning 200 person-days of work for a quarter and you have 5 engineers, that’s 200 ÷ 5 = 40 working days per person — about right for a quarter (assuming ~50 productive working days per person per quarter after PTO and overhead). If you’re planning 350 person-days, you’re over-committed and need to cut scope or add people.
2. Is anyone overloaded or underutilized?
Look at task assignment distribution. If one engineer has 15 tasks in progress and another has 2, something is off. This doesn’t require a spreadsheet — it requires a task board where assignments are visible.
FlowEra’s assignee filter makes this visible: filter the board by assignee to see each person’s workload. If the column is overflowing for one person and empty for another, rebalance.
3. Are there skill gaps for upcoming work?
If next quarter’s roadmap includes a major database migration and nobody on the team has deep PostgreSQL experience, that’s a resource gap that needs to be addressed — through hiring, training, or contracting. This is strategic resource planning, and it happens at the quarterly level, not the weekly level.
Assignment-Based Planning
Instead of pre-allocating people to projects in a spreadsheet, assign tasks to people as part of sprint planning and let the board reflect reality:
- During sprint planning, assign tasks based on expertise, availability, and development goals
- Use the board’s assignment view to see who has how much work
- Rebalance mid-sprint if someone finishes early or gets blocked
This is assignment-based planning: the task board is the resource plan. It’s always current because the team updates it as part of their normal workflow.
WIP as a Capacity Signal
WIP (work in progress) per person is a more useful capacity signal than planned hours. If someone has 5 tasks in progress simultaneously, they’re likely context-switching too much and none of the tasks are moving efficiently. If someone has 1 task and it’s blocked, they have available capacity.
FlowEra’s WIP tracking per person (through assignee filters) and per column (through WIP limits) gives you real-time capacity signals without a separate planning tool.
Planning for Unplanned Work
Every team does unplanned work — bugs, production incidents, urgent customer requests. The mistake is planning as if unplanned work won’t happen.
Reserve 20–30% of team capacity for unplanned work. If your team has 200 person-days per quarter, plan 140–160 person-days of feature work. The remaining capacity absorbs unplanned work. If the quarter is unusually quiet on the unplanned front, pull additional items from the backlog.
This buffer isn’t waste — it’s resilience. A team with no buffer absorbs every unexpected event by pushing planned work out, creating cascading delays and eroding trust in delivery commitments.