The project life cycle describes the phases a project goes through between the initial idea and the final review. The PMI framework (PMBOK) distinguishes five: initiation, planning, execution, monitoring and controlling, closure. The breakdown applies to an IT project as much as to a construction site or a reorganisation: what changes is how long each phase lasts and how they are chained. This guide details each phase, its deliverables, the questions to settle before moving on, and shows how the cycle adapts in predictive, agile and hybrid approaches.
The 5 phases of a project in one table
Each phase produces deliverables and ends with an exit question. Until the answer is yes, the project does not move to the next phase.
| Phase | Objective | Key deliverables | Exit question (go/no-go) |
|---|---|---|---|
| 1. Initiation | Decide whether the project deserves to exist | Project charter, business case, named sponsor, identified stakeholders | Are the need, the expected benefits and the budget envelope validated by the sponsor? |
| 2. Planning | Define how to reach the objective | WBS, schedule and milestones, budget, workload plan, risk register, communication plan | Is the plan realistic with the resources actually available? |
| 3. Execution | Produce the deliverables | Intermediate deliverables, meeting minutes, decisions, change management | Do the deliverables meet the acceptance criteria? |
| 4. Monitoring and controlling | Measure the variance and correct | Status reports, schedule/cost/quality indicators, corrective actions | Is the variance still within the agreed tolerances, or does it need re-arbitration? |
| 5. Closure | Finish cleanly and capitalise | Acceptance sign-off, handover to operations, project review, lessons learned | Has the client signed off and have the lessons been shared? |
Phase 1: initiation, or why this project
Initiation turns a request into a candidate project. The sponsor states the problem to solve, the expected benefits and the constraints (deadline, budget, regulation). The prospective project manager writes a one- or two-page project charter: objectives, scope in and out, stakeholders, assumptions, order of magnitude of costs. This is the document on which the committee decides to launch, postpone or drop. A well-run initiation takes a few days, not a few months. Frequent mistakes:
- Launching the project without an identified sponsor: nobody to decide when trade-offs arrive.
- Confusing solution and need: framing “deploy tool X” instead of “cut order processing time”.
- Skipping the business case because the decision is “already made”.
Phase 2: planning, from scope to workload plan
Planning translates the charter into an executable plan. The scope is broken down into work packages and tasks (WBS), workloads are estimated, tasks are chained with their dependencies, milestones are set and the critical path is identified. The workload plan then checks this schedule against the resources actually available, leave and other projects included. The phase ends with the kick-off meeting, which aligns the team and stakeholders on the plan. Frequent mistakes:
- Planning with resources at 100% when they are shared across several projects.
- Detailing the schedule day by day over 18 months: it will be wrong by week three.
- Forgetting external milestones (legal approval, supplier availability) that do not depend on the team.
Phase 3: execution, producing the deliverables
Execution is the longest phase and the one that consumes most resources. The project manager assigns tasks, removes blockers, runs team meetings and handles change requests: any scope change goes through an impact assessment on schedule and cost before being accepted. Decisions taken in meetings are logged with their date and owner, so they are not replayed. Frequent mistakes:
- Accepting “small” requests without logging them: the scope grows while the budget does not.
- Leaving decisions in mailboxes instead of a shared register.
- Waiting for the end of the phase to show a deliverable to the client.
Phase 4: monitoring and controlling, measuring the variance
The PMI speaks of a process group rather than a phase: monitoring and controlling runs alongside execution, from the first day to the last. It consists of regularly comparing actuals to the plan on three axes — schedule, cost, quality — and deciding on corrections. Concretely: weekly progress update, time recording, budget spent versus committed, risk review, and a one-page status report (the project weather) for the committee. Monitoring exists to act early: a delay flagged at 10% can be recovered, at 40% it is endured. Frequent mistakes:
- Tracking progress by feel (“we are at 80%”) rather than by remaining work.
- Producing a 20-page report nobody reads, instead of one page with three indicators and two decisions needed.
- Raising alerts only once the milestone has been missed.
Phase 5: closure, finishing and capitalising
Closure starts with final acceptance: the client or business checks that the deliverables meet the acceptance criteria set during planning, then signs off. Then come the handover to operations (documentation, training, support), administrative closure (contracts, invoices, releasing resources) and the project review: variances between planned and actual, causes, lessons. A closure that is not formalised leaves a project “95% done” that keeps consuming time for months. Frequent mistakes:
- Releasing the team before acceptance, then finding nobody to fix defects.
- Holding the review six months later, when nobody remembers the causes.
- Measuring expected benefits at closure: they often appear only after several months of operation, hence a deferred benefits review.
Predictive, agile or hybrid life cycle: what changes
The five phases exist in every approach, but their sequencing differs. In predictive (waterfall, V-model), each phase finishes before the next and the scope is frozen early. In iterative or agile, planning, execution and monitoring repeat every sprint and the scope is refined release after release. Hybrid, the most common in companies, frames and closes in predictive mode and executes in agile. The choice depends on how stable the need is and on the cost of a late change.
| Approach | When to use it | How the cycle changes | Example |
|---|---|---|---|
| Predictive | Stable need, regulatory constraints, high cost of error | Sequential phases, go/no-go gate between each phase, scope frozen after planning | Construction, infrastructure migration, fixed-price contract |
| Agile / iterative | Need discovered along the way, software product, frequent user feedback | Short initiation, then 2- to 4-week planning-execution-monitoring cycles; closure by stopping iterations | Business application, website, digital product |
| Hybrid | Organisation with committees and annual budgets, but agile delivery teams | Framing, budget and contractual milestones in predictive; delivery in sprints; mixed monitoring (milestones plus velocity) | ERP or CRM rollout, transformation programme |
Worked example: rolling out a management tool in an SME
A 120-person SME wants to replace its spreadsheets with a project tracking tool. Here is the full life cycle, in five steps:
- Initiation (2 weeks): management notes that the executive committee has no consolidated view of projects. The CIO writes a charter: objective “an up-to-date portfolio view every Monday”, scope limited to projects over 20 days, target budget €40k, sponsor the CEO. Go from the executive committee.
- Planning (3 weeks): WBS in four work packages (configuration, data migration, training, rollout), 4-month schedule with three milestones, workload plan of 0.3 FTE for the CIO and 0.5 FTE for a project manager, main risk “buy-in from project leads”.
- Execution (3 months): configuration in two iterations validated with two pilot project leads, migration of 25 projects, one change request (add budget tracking) accepted after being costed at +6 days.
- Monitoring and controlling (continuous): 30-minute weekly meeting, monthly project weather to the executive committee, alert in month two on a data migration delay, resolved by shifting training by one week without touching the final milestone.
- Closure (2 weeks): acceptance signed by the CEO on the criterion “portfolio up to date three Mondays in a row”, handover to internal support, review: €44k spent (+10%), deadline met, lesson “involve the pilots from the framing stage”.
The gates to formalise in a committee
A phase gate is a decision, not a date. For it to play its role, each gate has an input document, a body that decides and a written record. Template to reuse:
- Launch go (end of initiation): charter validated, sponsor named, envelope reserved. Body: executive committee or portfolio committee.
- Delivery go (end of planning): schedule, budget and workload plan accepted, major risks covered. Body: steering committee.
- Intermediate reviews (during execution): at each major milestone, project weather, decisions needed, change requests to arbitrate. Body: steering committee, at the rhythm set during framing.
- Go-live go (end of execution): acceptance pronounced, cutover and rollback plans ready. Body: steering committee extended to business and operations.
- Closure (end of project): review presented, resources released, benefits to measure with a date. Body: portfolio committee.
The life cycle at portfolio level
A project is not born in initiation: it was first an idea or a request among others. At portfolio level, the life cycle widens to five stages: idea, qualification, arbitration, project, review. Qualification checks alignment with strategy and estimates workload and benefits. Arbitration compares candidates with available capacity and decides which ones start, and when. The project then follows its five phases. The review closes the loop: the benefits actually obtained and the lessons feed the qualification of the next ideas. This wider cycle avoids launching more projects than the organisation can execute, which is the first cause of cascading delays.
In FoxPlan
FoxPlan covers this cycle end to end, from portfolio to project. Ideas and requests are collected, qualified and arbitrated before becoming projects. Planning relies on an interactive Gantt with dependencies, milestones and critical path, checked against resource capacity in a multi-project workload plan. Steering committees and project committees have their own module, with recurring sessions and agendas, and the project weather provides the status report for each review. Risks, decisions, actions and changes are tracked as project objects through to closure, whose review stays visible in the portfolio.
See how to do it in the FoxPlan documentation ↗
Frequently asked questions
What are the 5 phases of a project?
According to the PMI, the five phases (process groups) are initiation, planning, execution, monitoring and controlling, and closure. Monitoring and controlling is not strictly sequential: it runs in parallel with execution, from the first day to the last.
What is the difference between the project life cycle and the product life cycle?
The project life cycle ends at closure, once the deliverables are accepted. The product life cycle continues: operation, evolutions, retirement. A single product usually goes through several successive projects over its life.
How long does each phase of a project last?
There is no fixed rule. In practice, execution takes the largest share, often more than half the total duration; initiation and planning together represent a few weeks on a project of several months; closure lasts a few weeks. What matters is that every phase ends with an explicit decision.
Does the project life cycle apply to agile projects?
Yes. Initiation and closure remain, but planning, execution and monitoring repeat in each iteration of two to four weeks. The scope is refined release after release instead of being frozen at the start.
What is a go/no-go gate?
It is a decision point at the end of a phase where a committee decides to continue, adjust or stop the project. The decision relies on the phase deliverables (charter, plan, acceptance report) and is recorded in writing.
What is the life cycle of an IT project?
An IT project follows the same five phases, with execution often split into design, development, testing and deployment. Most IT projects today run a hybrid cycle: predictive framing and milestones, agile delivery in sprints.
