Initiation
Establish sponsor intent, the mandate and the governance around it, get the business case approved and stand the team up. Initiation ends when there is authority to plan and someone accountable for the outcome.
A practical structure for delivering complex technology and business change: five phases give the work shape, four gates give it assurance. The model is a deliberate PRINCE2 + Agile hybrid - predictive stage gates for the steering layer, agile cycles with defined delivery goals inside the team. Where a client has its own project management methodology, Vantage Meridian works to it, so this is the default rather than a condition of engagement.
Waterfall on the outside, agile on the inside. Senior leadership sees a predictive, gated project with tolerances and a paper trail, while the team runs short cycles (sprints) inside each phase, aligned to the phase objectives.
Establish sponsor intent, the mandate and the governance around it, get the business case approved and stand the team up. Initiation ends when there is authority to plan and someone accountable for the outcome.
Build the control baseline: the project plan and schedule, the RAID log and the bottom-up financial model. The delivery goals the team will work to are fixed here, which is what makes the agile layer underneath accountable.
The team runs iterative cycles - plan, build, review, refine - against the delivery goals set at Planning, through design, build, test and cutover. The control layer above keeps reporting to its own cadence while the cycles run.
The traditional monitor-and-control phase, run after Delivery and before Closure. Hypercare, operational acceptance, benefits tracking and the financial reconciliation - the phase where the claim made in the business case gets tested against live running.
Handover to the business, final reconciliation, lessons captured and the project formally closed. There is no gate out of Closure: it ends with the End Project Report signed off, because closure is the exit rather than another decision to take.
Each gate is a named decision with a named decider, and each one closes a phase. There is no gate out of Closure - the project ends with the End Project Report signed off. Gates sit in the control layer, so the team keeps working to its cycle while the decision is taken.
Every engagement artefact maps to a phase and a gate, and the articles work through how the phases play out in practice. The governance is sized to the work, not applied by rote. Consulting picks up where the framework leaves off.