Schedule First or Resource Planning First?¶
Decision¶
Create a technically plausible schedule first. Then add resource demand and capacity checks. In capacity-critical projects, schedule planning and resource planning then continue iteratively.

Why the Schedule Comes First¶
Resource demand arises from tasks, time periods, and effort. If tasks, subprojects, and dependencies are not yet plausible, capacity calculation is not reliable either.
Start with:
project structure
tasks
milestones
dependencies
critical path
float and reserve times
When to Include Resources Earlier¶
Resources should be considered early when:
a few key people determine the project date
specific professional qualifications are scarce
machinery or equipment is limiting
several projects use the same resource pool
the finish date can only be reached with realistically available capacity
Recommended Sequence¶
Build project structure and scheduling logic.
Plan rough resource demand by professional qualification.
Perform capacity balancing.
Stabilize the schedule based on identified bottlenecks.
Assign employees bindingly.
Check utilization and date impact again.


Decision Table¶
Situation |
Approach |
|---|---|
New project without scheduling logic |
Schedule first |
Project with known bottleneck resources |
Schedule and resources iteratively |
Rough feasibility check |
Plan role demand early |
Binding employee planning |
After capacity check |
Portfolio with several projects |
Include resource planning early |