Blog Capacity
Before accepting a project: how to check whether the team can deliver
You need three numbers: the hours the project will need each month, the free hours your team has in those months, and a buffer. Almost nobody has the second one.
A worked example
A team of six has 780 productive hours in March after holidays, leave and internal time. Current projects are allocated 640. That leaves 140. The new project needs 180 in March. It does not fit — and you would never see it by looking at headcount. The figures are illustrative.
Keep a buffer
Planning everyone at 100% guarantees that the first thing that slips is paid for by another project. Ten to fifteen percent unallocated is what absorbs change.
How Fichaloto does it
Capacity comes from each person’s working hours minus holidays and approved leave, allocations carry a percentage, and the coverage-gap view shows upcoming demand against what is left. Capacity planning.
Frequently asked questions
How much capacity buffer should a team keep?
As a rule of thumb, ten to fifteen percent unallocated, more when scope is loosely defined.
All of this is built into Fichaloto. See how it works.
Keep reading
Capacity
Planned, clocked, charged: three numbers that should match and usually do not
Most companies can tell you what they planned and what they invoiced. Very few can tell you, for a given week, whether those two things are related.
Capacity
The resourcing meeting costs more than you think
Nobody budgets for this meeting. It is the most expensive one you run and the one that produces the fewest decisions per minute spent.
Capacity
Being allocated at a hundred per cent is not billing at a hundred per cent
Most arguments about utilization are really arguments about what is being measured, and nobody has said so out loud.