Project to product
New functionality is delivered as a project: from proposal to go-live, through early life support and stabilisation, to a formal handover. From then on the Product layer owns it and improves it continuously.
Project or product? The mode test
Triage applies this test to every request. It is a project if any of these apply:
- A new system, module, site or service goes live
- It needs its own business case or funding
- It needs cutover or training at scale
- It is estimated at more than six months
Several projects sharing one outcome, or several organisations, form a programme. Everything else is a product change and follows the demand-to-value flow.
The eight phases
Propose
A request for new functionality enters the front door. Triage identifies it as a project, and an outline case sets out the problem, options and rough cost.
Ends at: G0 Proposal approvedDefine
The business case, project charter, scope and plan are agreed. The Receiving Product Manager is named, and the safety and compliance plan and data protection screening start.
Ends at: G1 Business case approvedDesign and build
Configuration, integration and data migration are designed and built in sprints. The Design Authority rules on design, and the hazard log and test evidence grow.
Ends at: G2 Test exit and ready to preparePrepare
Training is delivered, cutover is rehearsed, data is trial-loaded, services confirm readiness, and the early life support plan and support model are in place.
Ends at: G3 Go / No-GoGo-live
The cutover runbook is executed. Rollback criteria are checked at every checkpoint until the service is confirmed live.
Ends at: Live confirmedEarly life support
A command centre and floorwalkers support staff. Daily huddles track incidents, safety concerns and quick fixes against the exit criteria.
Ends at: G4 ELS exitStabilise
Defects are burned down, performance and adoption improve, and the handover pack is prepared while the product team shadows.
Ends at: G5 Handover acceptedHandover and close
The Product layer accepts the product and owns all change from the next day. The project closes with lessons learned and releases its team.
Ends at: ClosedAligned with PRINCE2 and ITIL
Each phase is a PRINCE2 management stage, and each gate is a stage boundary where the Project Board decides whether to continue. The route into live service follows ITIL change enablement, release and deployment management, early life support and operational acceptance. See PRINCE2 and ITIL alignment for the full mapping.
After handover
The project team disbands or moves to its next project. The Product layer owns the product, its backlog, hazard log and benefits, and improves it through the demand-to-value flow. See Handover for the full guidance.
The rest of this page is for subscribers
Subscribe to read the other 3 sections of this page:
- Gate criteria
- Who is involved at each phase
- Sprints inside gates