What does a person-day measure?
A person-day measures the total human work required to complete an activity. If one person needs one full working day to perform a task, that task may be estimated as roughly one person-day. Two people working half a day each can also add up to one person-day of effort.
The unit does not tell you when the task will finish. A five person-day analysis can still span two calendar weeks if interviews, data availability, approvals or dependent activities create waiting time.
How do you calculate person-days?
A useful estimate starts by breaking the work into activities and summing the effort required for each one. Good estimates include not only direct production work but also analysis, meetings, coordination, testing, corrections, documentation and project management.
| Work package | Estimated effort |
|---|---|
| Analysis | 8 person-days |
| Design | 6 person-days |
| Implementation | 16 person-days |
| Testing and fixes | 8 person-days |
| Closure and documentation | 2 person-days |
| Total | 40 person-days |
How many hours are in one person-day?
There is no universal conversion. If your organization defines a standard working day as eight hours, one person-day equals eight person-hours. Other organizations may use 7.5 hours or another standard, so proposals and contracts should state the conversion explicitly.
Person-days versus project duration
Effort is the total amount of human work. Duration is the elapsed schedule time between start and finish. Forty person-days of effort may finish in twenty working days if activities can overlap, or it may take longer than forty calendar days when approvals and sequential dependencies dominate.
Why 100 person-days divided by five people is not always 20 days
The arithmetic is valid only when the work can be divided cleanly, the necessary skills are available in parallel and each person has the assumed capacity. Real projects often contain sequential work, specialist bottlenecks, approval windows and coordination overhead.
- Sequential predecessor-successor activities
- Specialist or role-specific bottlenecks
- Customer or management decisions
- Testing and acceptance windows
- Knowledge transfer and coordination overhead
- People split across multiple projects
Examples across different project types
In software delivery, 2 person-days of analysis, 2 of design, 6 of development, 3 of testing and 1 of documentation total 14 person-days. Two developers do not automatically reduce elapsed time to seven days because analysis and testing may remain sequential.
In consulting, interviews, data analysis, solution design and management presentations may total 45–50 person-days but span six weeks because client calendars and decision lead times drive duration.
In engineering, mechanical, electrical and controls work may partly overlap, while interface decisions and technical reviews create dependencies that determine the schedule.
What should a good person-day estimate include?
A credible estimate should show the work breakdown and assumptions rather than only one total number. It should identify which roles perform the work, what is excluded, how much coordination and testing are included, and which dependencies may change the schedule.
- Effort by work package
- Role and skill distribution
- Scope assumptions and exclusions
- Testing, coordination and project-management effort
- Uncertainty and risk allowance
- Actual resource capacity
- Schedule dependencies and critical path