Team Capacity Planning with a Kanban Board: A Weekly Workload Planning Method

Overview

A kanban board is more than a visual list of tasks. Used consistently, it can act as a lightweight resource planning board: the team can see work already in progress, compare demand with available time, and set a practical limit on new intake.

The goal is not to fill every person’s calendar. The goal is to make a defensible planning decision: which work should move next, who is best placed to take it, and what must wait? Capacity planning is especially useful for software, infrastructure, support, and operations teams where planned project work competes with incidents, reviews, meetings, and maintenance.

Use one unit of measurement across the worksheet. Hours are useful when tasks have reasonably clear effort estimates. Relative points can work for teams that already estimate consistently. Do not mix hours and points in the same calculation. If estimates are uncertain, use ranges or mark the task as needing clarification instead of presenting a precise number that the team does not trust.

Your kanban board should make at least these states visible:

• Ready: prioritized work that could be started.
• In progress: work currently consuming team capacity.
• Blocked: work that cannot advance without a decision, dependency, or external input.
• Review or validation: work awaiting testing, approval, or operational checks.
• Done: work that meets the team’s definition of complete.

These columns help distinguish available capacity from apparent capacity. A person with three tasks in progress may have no practical room for another assignment, even if their calendar looks open.

What to track

1. Available capacity by owner

Start with each person’s working capacity for the planning period. Then subtract time that is unavailable for planned board work. A simple formula is:

Available capacity = working capacity − leave − support duty − fixed commitments − planning buffer

The buffer is intentional room for interruptions, coordination, small requests, and estimation error. Its size should be agreed by the team rather than treated as hidden spare time. Teams with frequent operational work may need a larger buffer than teams working in a more predictable environment.

2. Unfinished work

At the start of the week, review every item still in progress. Record its remaining effort rather than its original estimate. If the remaining effort is unknown, ask what specific step is left and estimate that step. A task that is 90% complete but waiting for review still consumes review capacity and may block downstream work.

Do not automatically carry every unfinished item forward as a fresh commitment. Confirm whether it remains important, whether it is blocked, and whether its owner is still the right person. This prevents old work from silently consuming the next week’s entire capacity.

3. Demand from ready work

Estimate the work you are considering for the week, then rank it before assigning it. Priority should reflect business impact, urgency, dependencies, risk reduction, and the cost of delay—not simply who requested the task first. A task prioritization tool or a simple scoring method can make trade-offs easier to explain.

Only pull work into active columns when the team has capacity and the task meets the board’s readiness criteria. If you need to track a larger queue, keep it in a clearly defined backlog rather than allowing the ready column to become an unbounded list.

Reusable team capacity worksheet

Copy this structure into a spreadsheet, database, or custom view in your kanban board software. Use the same planning period for every row.

In this example, available capacity is calculated before unfinished work is deducted. The new work allowance is available capacity − unfinished work. If the result is zero or negative, do not assign new planned work to that owner without removing, reassigning, or renegotiating an existing commitment.

Workload-by-owner table

Use a second table to test the proposed assignment rather than relying on a visual impression of the board.

Capacity is not a reason to assign work mechanically. Check skills, dependencies, review responsibilities, and whether concentrating too much work with one person creates a bottleneck. A balanced plan can still leave some capacity unused if that protects flow or provides coverage for a critical system.

Cadence and checkpoints

Run the main capacity review once a week on a consistent day. A short, repeatable routine is more useful than an occasional planning meeting that attempts to predict several months of work.

1. Refresh the board. Move cards to their actual workflow states, close completed items, identify stale cards, and mark blockers. A backlog cleanup review can help separate active work from abandoned or obsolete requests.
2. Review unfinished work. For each in-progress item, confirm the remaining effort, next action, owner, and dependency. Split work that is too large to forecast clearly.
3. Record availability changes. Add leave, on-call or support rotations, training, release duties, recurring meetings, and other fixed commitments. Treat partial-day changes as real capacity changes.
4. Calculate capacity. Apply the worksheet formula for each owner. Use either hours or the team’s established estimation unit, and record assumptions where the figure is uncertain.
5. Set the intake limit. Compare ready work with the total new-work allowance. Pull only the highest-priority items that fit. If the team uses WIP limits, check that proposed assignments also respect those limits.
6. Confirm ownership and handoffs. Make sure every selected task has a clear owner, acceptance criteria, and known reviewer or dependency.
7. Publish the decision. Leave the board as the shared record of what is active, what is ready, and what is intentionally deferred.

Between weekly reviews, update the board when a major incident, urgent request, absence, or dependency changes the plan. Avoid silently adding work. Add it to the intake queue, identify its priority, and show what will move out if it must enter immediately.

For teams that work remotely or across several systems, connected kanban software can reduce manual updates. Rules may flag overdue work, notify owners when cards are blocked, or create follow-up tasks from operational events. Automation should expose changes in capacity; it should not make unreviewed commitments on the team’s behalf. See the guide to workflow automation for kanban boards for examples of useful rules.

How to interpret changes

A single over-capacity week is a signal to investigate, not proof that the planning method has failed. Look for patterns across several planning cycles.

• Repeated carryover: Work may be oversized, estimates may be optimistic, or interruptions may be missing from the worksheet. Review cycle time and throughput alongside capacity rather than judging the team by completed task count alone.
• Large unused capacity: The team may be protecting a sensible buffer, or ready work may be poorly prepared. Check whether tasks lack acceptance criteria, have unresolved dependencies, or are ranked too low to justify starting.
• One owner is consistently overloaded: Rebalance assignments, improve documentation, rotate support duty, or address a skill constraint. Simply adding more tasks to the board will not remove the bottleneck.
• Work starts but does not finish: Inspect WIP limits, review queues, and blocked states. Limiting active work can improve flow when too many simultaneous tasks are competing for attention. Use the kanban WIP limits guide to review the mechanics.
• Urgent work repeatedly displaces planned work: Reserve explicit support capacity and define what qualifies as urgent. If every request is expedited, the board is not showing priorities clearly.
• Estimates vary widely: Improve task slicing and estimation language before attempting more detailed forecasting. Capacity planning is only as useful as the assumptions behind it.

Use the board’s history, if available, to compare planned work with completed work, blocked time, and carryover. These observations can inform the next worksheet without turning the team’s measures into individual performance scores. Capacity planning works best as a coordination tool, not a way to pressure people into filling every available hour.

When to revisit

Revisit the worksheet every week before selecting new work. Also review the method monthly or quarterly, depending on how quickly the team’s work changes. Update it sooner when team membership, working hours, support coverage, release responsibilities, estimation units, or board columns change.

At a monthly or quarterly review, ask:

• Are the worksheet formulas still using the same capacity unit and planning period?
• Are leave, support duty, meetings, and recurring operational work being recorded consistently?
• Does the buffer reflect actual interruptions, or is it masking a structural problem?
• Are unfinished tasks being carried forward with fresh estimates and clear next actions?
• Do WIP limits, automation rules, integrations, and board states still match the team’s workflow?
• Are completed-work and cycle-time patterns consistent with the commitments being made?

Refresh the example values and terminology whenever your planning practices or kanban board software capabilities change. Before each weekly session, spend a few minutes cleaning the board, updating owner availability, and checking the new-work allowance. Then make one explicit decision: what will enter, what will wait, and what existing commitment must change if a new priority is accepted.

That recurring discipline turns a kanban board into a practical team workload planning system. It keeps capacity visible, makes trade-offs easier to discuss, and gives the team a realistic intake limit without requiring a complex resource planning process.