The project life cycle is the sequence of phases a project moves through from idea to completion. The most widely used model has five phases: initiation, planning, execution, monitoring and controlling, and closure. Knowing what belongs in each phase helps you avoid the most common project failures: unclear goals, weak plans and projects that never formally end. Our project management course works through each phase with practical tools.
The 5 phases of the project life cycle
1. Initiation
The project is defined and approved. The key question: should we do this at all?
- Activities: clarify the problem or opportunity, outline the scope, identify stakeholders, estimate cost and benefit at a high level.
- Outputs: a business case and a project charter (or project brief) that names the sponsor, objectives and success criteria.
- Common mistake: starting work before the objectives and sponsor are agreed.
2. Planning
The team works out how the project will be delivered.
- Activities: break the work into tasks, estimate time and cost, set the schedule, assign roles, plan communication and identify risks.
- Outputs: a project plan, schedule (often a Gantt chart), budget, risk register and communication plan.
- Common mistake: planning in too much detail too early, or too little, with no realistic estimates.
3. Execution
The team does the work and produces the deliverables.
- Activities: coordinate people and resources, manage suppliers, hold regular team meetings and keep stakeholders informed.
- Outputs: the project's deliverables, plus status updates and decision logs.
- Common mistake: letting new requests into the scope without assessing their impact on time and cost.
4. Monitoring and controlling
This runs alongside execution. The project manager compares progress with the plan and acts on any gaps.
- Activities: track schedule, budget and quality, manage change requests, update the risk register and report to the sponsor.
- Outputs: progress reports, approved change requests and corrective actions.
- Common mistake: reporting "green" until it is too late to recover.
5. Closure
The project is formally finished and handed over.
- Activities: confirm the deliverables are accepted, hand over to the people who will run them, release the team, close contracts and review lessons learned.
- Outputs: acceptance sign-off, handover documents and a lessons-learned report.
- Common mistake: projects that drift on with no clear end, or end without capturing lessons for next time.
Project life cycle at a glance
| Phase | Key question | Main outputs |
|---|---|---|
| Initiation | Should we do this? | Business case, project charter |
| Planning | How will we deliver it? | Plan, schedule, budget, risk register |
| Execution | Are we building it? | Deliverables, status updates |
| Monitoring and controlling | Are we on track? | Progress reports, change log |
| Closure | Is it done and handed over? | Sign-off, lessons learned |
Different organisations name the stages differently. APM in the UK and PRINCE2 use their own terms, and some models split the cycle into four or seven stages, but the logic is the same: decide, plan, deliver, control and close.
Predictive and agile life cycles
The five phases above describe a predictive (or waterfall) life cycle, where most planning happens up front. It suits projects with stable, well-understood requirements, such as an office move or a regulatory change.
An agile (iterative) life cycle repeats short cycles of planning, building and reviewing, delivering usable results in small increments. It suits projects where requirements will change, such as software or new digital services.
Many projects use a hybrid: a fixed overall plan and budget, with agile delivery inside it.
Project life cycle vs product life cycle
A project life cycle ends when the project is closed. A product life cycle (introduction, growth, maturity, decline) covers the whole life of a product in the market, which may include many projects. A software development life cycle (SDLC) describes the stages of building software and can sit inside a project's execution phase.
How to use the life cycle on your next project
- Hold a clear gate between phases. Do not start planning until the sponsor has approved the charter, and do not start execution without an agreed plan.
- Keep the risk register alive. Review it at every progress meeting, not just at the start.
- Control scope. Run every change through a simple change request: what it adds, what it costs and who approves it.
- Plan the closure from the start. Define what "done" looks like and who will accept it.
- Capture lessons as you go, not only at the end, when people have already moved on.
Frequently asked questions
What are the 5 stages of a project life cycle?
Initiation, planning, execution, monitoring and controlling, and closure.
What is the difference between the project life cycle and the project management process?
The life cycle is the sequence of phases the project passes through. Project management processes, such as risk management or stakeholder communication, are the activities the project manager carries out across those phases.
Which phase is the most important?
Initiation and planning have the biggest influence on success, because errors made there are the most expensive to fix later.
Do I need a qualification to manage the project life cycle?
No, but structured training helps. A practical course builds the core skills, while certifications such as PRINCE2 or PMP test a specific method. Read project management course or PRINCE2? to compare the routes.
If you manage projects as part of a wider role, our project management course in London and online covers planning, risk and stakeholder management with practical tools.