| Phase | Mark | Jerry | Chhojun | Andrew | Hajra | Available |
|---|---|---|---|---|---|---|
| Spec | ✓ | ✓ | ✗ | ✗ | ✗ | 2 |
| Dev | ✓ | ✓ | ✓ | ✗ | ✗ | 3 |
| Test | ✓ | ✓ | ✗ | ✓ | ✗ | 3 |
| Deploy | ✓ | ✓ | ✗ | ✓ | ✗ | 3 |
| Docs | ✗ | ✗ | ✗ | ✓ | ✓ | 2 |
Red bars = Actual demand | Green lines = Maximum feasible capacity
Outcome: All team members perform at peak efficiency, no unexpected delays, perfect task handoffs.
Timeline: 42 weeks | Resource utilization: 501/210 person-days (2.39x capacity)
Key assumption: Zero rework, optimal skill matching, no external dependencies
Outcome: Mixed efficiency levels, 15-20% rework factor, typical bottleneck delays in Spec/Docs phases.
Timeline: 58 weeks | Resource utilization: 650/210 person-days (3.1x capacity)
Critical risks: Documentation backlog, specification review delays, testing queue buildup
Outcome: Significant skill mismatches, 30%+ rework, team member unavailability, scope creep.
Timeline: 85+ weeks | Resource utilization: 1,227/210 person-days (5.85x capacity)
Failure points: Spec bottleneck breakdown, cascading delays, quality compromises