Part of the Time & Productivity suite · 32 calculators

Project Timeline Calculator

How long a project takes from the effort it needs, the people on it and the coordination overhead that adding people creates.

Effort divided by people gives an elapsed time only if people were interchangeable and communication were free.

%
%
Results update as you type
Results
Elapsed working days
81.63
Calendar weeks
Effective people after overhead
Team efficiency
Communication paths
Team size that finishes soonest
Elapsed days at that size
Elapsed days with one person
Reviewed September 2026. Calendar arithmetic: the same result in every country; dates shown as year-month-day to avoid day/month confusion. The US writes dates month/day/year.
No account required · Google Analytics off unless allowedCalculator arithmetic runs in your browserResults update as you type
All calculations run 100% in your browser. The calculator code does not submit your figures to GlobalCalc to obtain a result.
About project timeline

How the project timeline calculator works

Effort divided by people gives an elapsed time only if people were interchangeable and communication were free. They are not. Communication paths grow as n(n−1)/2, so each person added contributes less than the last.

That is Brooks's observation in arithmetic form. Past a certain team size the overhead exceeds the added capacity and the project gets slower, which this shows as an optimal team size rather than as advice.

Formula: elapsed = effort / (people × efficiency); efficiency falls with team size

Worked examples

InputsElapsed working daysNote
240 person-days across five people81.63about 71 days
A large team228.57slower than a smaller one
Full availability57.14a third faster

Frequently asked questions

Why does adding people not halve the time?

Because coordination costs grow with the square of team size while capacity grows linearly. Past a point the next person makes the project slower.

What is the ideal team size?

For most software and creative work, five to nine. This calculator finds the size that finishes soonest given your own overhead figure.

What availability should I assume?

Sixty to eighty per cent for people who also have meetings, support duties and another project. A hundred per cent is fiction.

Is this Brooks's law?

It is the arithmetic behind it. Brooks's point was about adding people to a late project, where ramp-up makes it worse still.

Does the effort estimate include testing?

Only if you put it there. Effort estimates that count development but not review, testing and deployment are the usual reason projects overrun.

Where these figures come from

Last checked: September 2026. The Gregorian calendar rules do not change; working-day counts exclude Saturdays and Sundays only.