The Schedule Compression Squeeze
You are the project manager for a 9-month warehouse management system implementation with a fixed go-live date tied to a holiday peak season. The critical path currently runs 6 weeks past the committed date. Your sponsor has refused to move the date and has authorized overtime. The team has already been working 50-hour weeks for a month, and two senior developers have privately told you they are close to burnout. A vendor offers to accelerate a middleware integration for an extra $180,000, which would recover 4 weeks but introduces a dependency on their availability during the final month. Your cost contingency holds $250,000. The steering committee meets in three days and wants a recommendation, not options.
1. What recommendation should you bring, and how do you justify it against the available levers?
Read the worked answer
The defensible recommendation is a blended recovery plan, not a single lever. The math: you need 6 weeks; the vendor buys 4 weeks for $180k, leaving 2 weeks to recover internally. Pure overtime is the weakest lever here because the team is already at 50-hour weeks - productivity gains from further overtime are marginal and the burnout signals are a real risk to the critical path, not a soft concern. So:
- Accept the vendor acceleration ($180k, within the $250k contingency) to recover 4 weeks, with a contractual commitment on availability during the final month to manage the new dependency.
- Recover the remaining 2 weeks through scope re-sequencing - identify features that can move to a post-go-live phase without breaking the season-critical path, rather than adding more hours.
- Protect the team by capping hours and explicitly telling the steering committee that further compression carries schedule risk through attrition.
The justification frames each lever by its marginal return and its risk: overtime has diminishing returns and rising risk; vendor acceleration has a known cost and a manageable dependency; scope trade is the only lever that reduces work rather than compressing it. Presenting a single recommendation with residual risk stated is what the committee is asking for.
2. The sponsor pushes back: "Just add more people - we have budget." How do you respond, and what does that tell you about the constraint?
Read the worked answer
Adding people to a late project is the classic case of ignoring the critical path and ramp-up cost. New team members must be onboarded by the existing seniors - who are already stretched - so short-term throughput drops before it rises. On a project 6 weeks behind with a fixed date, there is rarely enough runway for that curve to pay back. The constraint is not headcount; it is critical-path duration and the existing team's capacity to absorb new work.
The response: acknowledge the budget, then redirect it to levers that act on the actual constraint - the vendor acceleration (which shortens the path directly) and scope re-sequencing (which shortens it by removing work). If the sponsor insists on adding staff, propose it only for non-critical-path work that can be parallelized without onboarding burden on the seniors, and state the expected payback window honestly. The judgment being tested is recognizing that throwing resources at a schedule problem fails when the bottleneck is the path itself and the team's absorption capacity.