Northgate Depot Refurbishment - choosing a life cycle under emerging requirements
Northgate is a 14-month, £3.2m project to refurbish a live distribution depot so automated picking can be installed while 400 staff continue to despatch orders. The operations director, who is also the sponsor, has mandated a linear stage-gate life cycle "because the warehouse build in 2019 ran that way". By the end of month 3 the design stage has overrun by seven weeks, roughly 45% of the fit-out requirements are still emerging from the operations team, and the fire-safety regulator has issued revised guidance on sprinkler zoning that affects the layout. Each gate review is turning into a re-planning workshop, and the lease on the temporary overflow site expires on 1 September, after which the depot cannot legally operate at current volumes.
1. Advise the sponsor on the most appropriate life cycle for this project, justifying your recommendation against what is actually happening on the ground.
Read the worked answer
Diagnosis. The two drivers of life-cycle choice are the degree of certainty in the scope and the rate of external change. Here both are poor: ~45% of requirements are still emerging after the design stage was supposed to close, and a regulator has changed a design constraint mid-flight. A pure linear life cycle assumes scope can be baselined early and change is exceptional; on this project change is normal, so each gate simply exposes rework that has already been paid for.
Recommendation - hybrid. Keep a linear outer framework (concept → definition → deployment → transition → benefits realisation) because the sponsor genuinely needs funding and lease-driven decision points, and the depot must be operational by 1 September. But run the fit-out design and the site-by-site installation as short iterative cycles with user walkthroughs, so that requirements are discovered before they are built rather than after a gate.
Why not pure iterative. The regulatory and lease milestones are fixed and non-negotiable; a fully exploratory approach would lose the control points the sponsor needs to release money and would not suit a physical construction/installation element.
Action. Record the chosen life cycle in the project management plan and explain to the sponsor that the overrun is a symptom of the model, not of the team's performance.
2. The sponsor asks: "When is this project finished?" Explain using the extended project life cycle, and say who is accountable for what after handover.
Read the worked answer
Answer. The project itself finishes at the end of the transition phase: installation complete, commissioned, staff trained, documentation and as-built records handed over, acceptance signed, resources released, and a closure/lessons-learned review held. That is where the project manager's accountability ends.
However, the reason the £3.2m is being spent sits in the benefits realisation phase, which runs after closure - reduced picking cost per order, higher throughput, fewer despatch errors. These do not appear on handover day; they accrue over months of operation.
Accountability split:
- Project manager - delivery to the agreed scope, cost, time and quality through transition, plus a benefits realisation plan and baseline measures handed to the business.
- Sponsor - owns the business case and stays accountable for the benefits; usually delegates day-to-day pursuit to a named benefit owner in operations.
- Business/operations - embeds the process changes (new picking routines, shift patterns, training refresh) that make the benefits possible.
Point to make to the sponsor. Closing the project on 1 September is a delivery milestone, not the point at which success can be judged. Book a benefits review at, say, 6 and 12 months post-handover, and name the benefit owner now rather than at closure.
3. The regulator's revised sprinkler guidance arrives in month 3. How should this be handled, and can the stage-gate structure help?
Read the worked answer
Treat it as a change to the baseline, even though it is not optional. The fact that a change is mandatory does not remove the need for impact analysis: cost of re-design and re-work, effect on the 1 September lease deadline, safety and quality implications, knock-on changes to the installation sequence, and the risk position.
Process:
- Record the guidance as a change request with the regulator's document as the driver (and note it as an external risk that has crystallised).
- Perform an impact assessment across scope, schedule, cost, quality and risk - not just "can we absorb it?".
- Assess the impact against the stage tolerances. If the cost/time impact exceeds the tolerance delegated to the project manager, it must be escalated to the sponsor/steering group as an exception rather than absorbed quietly.
- If approved, re-baseline the plan and update the design, the risk register and the assumptions log; then re-communicate.
Value of the gates. A stage gate is exactly the right place to confirm regulatory compliance before committing to installation. The weakness here is timing - the guidance arrived mid-stage, so it should trigger an off-cycle exception review rather than waiting for the next gate, which would waste weeks.