Guide
Project management life cycle phases — Malaysia
Every project moves through the same stages, and the useful question at each one is what must exist before moving to the next.
Updated 24 October 2026
The project management life cycle is the sequence a project passes through from the moment it is proposed to the moment it is closed. The common version has four phases: initiation, planning, execution and closure, with monitoring running alongside the work.
The point of naming the phases is not ceremony. It is to give each stage a gate: a short list of things that must exist before the project is allowed to move on, so problems are found while they are cheap to fix.
This guide describes each phase, what should exist at the end of it, and how it maps onto the five process groups in the PMBOK® Guide, the best-known framework for the field.
The project management life cycle phases at a glance
Four phases, each ending in something you can inspect.
| Phase | The question it answers | What should exist at the end |
|---|---|---|
| Initiation | Should this project exist, and who authorises it? | A signed charter with purpose, scope, sponsor, budget and key dates |
| Planning | How will it be done? | Work breakdown, schedule, budget, owners, risk list |
| Execution | Is the work being done to the plan? | The deliverables, plus regular progress reports |
| Closure | Is it finished, and what did we learn? | Accepted deliverables, handover, lessons recorded |
Initiation: deciding the project is worth starting
This is the phase most often skipped, and the one that prevents the most waste. It produces the project charter, the short document that formally authorises the project and names who is accountable.
A charter that cannot be written is information. If nobody can state the purpose in a few sentences or name a sponsor, the project is not yet clear enough to plan.
The charter template on this site builds one and shows which of the twelve essential sections are still empty.
Planning: working out how, before doing it
Planning turns the charter’s scope into detail. The work is divided into deliverables in a work breakdown structure, each piece is estimated and given an owner, and the dependencies between pieces are mapped so the schedule and the critical path can be calculated.
This is also where the budget is built from the estimates, the risks are listed and rated, and the way progress will be reported is agreed.
Planning ends when the sponsor approves the plan, because that approval is what makes later changes a conscious decision rather than a drift.
Execution and monitoring: doing the work and watching it
Execution is where most of the time and money goes: the team produces the deliverables. The project manager’s job in this phase is to clear blockers, keep the people aligned, and compare actual progress with the plan.
Monitoring is that comparison, done on a rhythm. Is each task finishing when scheduled? Is spend tracking to budget? Has a risk occurred? Has anyone asked for a change?
Change is normal. What matters is that each change request is assessed for its effect on scope, schedule and cost before anyone agrees to it, so the plan is updated deliberately.
Closure, and how the phases map to PMI’s five groups
Closure confirms that the sponsor accepts the deliverables, hands them over to whoever will run them, releases the team and records what the project taught. Skipping the last step is how the same mistakes are repeated in the next project.
The PMBOK® Guide groups project management processes into five process groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing, per PMI’s published library. They map directly onto the phases above, with Monitoring and Controlling shown as its own group that runs alongside the others rather than after them.
Neither view is more correct. The four-phase version is easier to explain to a team; the five-group version is the vocabulary used in PMI materials, so it is worth knowing if you read tenders or sit an exam.
Questions
›What are the phases of the project management life cycle?
Commonly four: initiation, planning, execution and closure, with monitoring and control running alongside the work. PMI’s PMBOK® Guide describes five process groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing.
›What is the difference between the life cycle and the process groups?
The life cycle describes the project’s stages in time. The process groups describe categories of management activity, which overlap in time. In practice the two are the same picture drawn two ways.
›What is produced in each phase?
A charter in initiation, a plan with work breakdown, schedule, budget and risk list in planning, the deliverables and progress reports in execution, and accepted deliverables plus recorded lessons in closure.
›Is the life cycle the same for agile projects?
The same activities happen, but they repeat in short cycles instead of once in sequence. The agile versus waterfall guide explains how the two approaches differ and where each fits.
›Why does the life cycle start with a charter?
Because it forces the purpose, scope, sponsor, budget and dates to be written down and agreed before any planning. If they cannot be written, the project is not yet clear enough to plan, and finding that out on day one is cheaper than finding it in month three.
Get a quote
Tell us your team size, timeframe and whether you pay the HRD Corp levy. Within one working day you get a day rate, a suggested course shape and how to claim it through HRD Corp.