The Project Life Cycle: the 5 Phases of a Project, Explained
By the end of this lesson you'll be able to:
- Name the five phases of the project life cycle in the right order
- Say what happens in each phase and what it typically produces
- Spot a skipped or rushed phase in a real project, and explain what it costs
Quick answer: what is the project life cycle?
The project life cycle is the series of five phases a project moves through: initiation, planning, execution, monitoring and controlling, and closing. In Kanbanchi's Project Management 101 course, you learn what happens in each phase, what each one produces, and what skipping one cost the Sydney Opera House.
The 5 project management phases in 8 slides
One idea per slide. Use the buttons, the dots or your arrow keys. The full text of every slide is right below the player.
Lesson 1 slides
8 slides
The full lesson: the project life cycle, phase by phase
What is the project life cycle?
The project life cycle is the series of five phases a project moves through: initiation, planning, execution, monitoring and controlling, and closing. Project managers also call them the project management phases. A project is a temporary effort with a defined start and end that creates a unique product, service or result. Because it is temporary, it has a beginning, a middle and an end, and each part needs different work.
Knowing the phases helps in two ways. It tells you what should be happening right now, and it shows you what is missing. If your team is building before anyone has agreed what "done" means, you have skipped part of initiation and planning, and the case study below shows what that can cost.
| Phase | What happens | Typical outputs |
|---|---|---|
| 1. Initiation | Decide why the project exists, what success looks like and who sponsors it. | A project charter and a stakeholder list |
| 2. Planning | Work out how the goal will be reached: scope, tasks, schedule, budget, risks and communication. | An approved project plan, the baseline |
| 3. Execution | The team does the work and produces the deliverables, starting with a kickoff meeting. | Deliverables and progress updates |
| 4. Monitoring and controlling | Compare progress with the plan, manage changes and fix problems early. It runs alongside execution. | Status reports and approved change requests |
| 5. Closing | Hand over the result, get formal acceptance, release the team and record lessons learned. | Sign-off, a final report and a retrospective |
Phase 1: Initiation
Decide why the project exists, what success looks like and who sponsors it. It answers one question: why are we doing this, and is it worth doing? A sponsor, the person who pays for or champions the project, agrees the goal, a rough budget and a rough timeline.
The main output is a project charter: a short document that names the goal, the sponsor, the project manager, the main deliverables and the known constraints. The second output is a stakeholder list, everyone who is affected by the project or can affect it. If the charter is missing, nobody can say later whether the project succeeded.
Phase 2: Planning
Work out how the goal will be reached: scope, tasks, schedule, budget, risks and communication. The team breaks the work into tasks (a work breakdown structure), estimates how long each takes, puts them in order on a schedule, sets the budget and lists the main risks.
The output is an approved project plan. Its agreed scope, schedule and budget become the baseline, the yardstick you will measure progress against in phase 4. Planning is where most of the cheap decisions happen: moving a task on paper costs nothing, moving it after the work has started can cost a lot.
Phase 3: Execution
The team does the work and produces the deliverables, starting with a kickoff meeting. The kickoff meeting launches the work with the whole team once the plan is approved. Some teams hold it at the end of planning; in this course it marks the start of execution.
During execution the project manager coordinates people, removes blockers, keeps stakeholders informed and makes sure deliverables meet the agreed quality. Most of the time and money in a project is spent in this phase.
Phase 4: Monitoring and controlling
Compare progress with the plan, manage changes and fix problems early. It runs alongside execution. It is listed fourth, but it does not wait for execution to finish: you track progress while the work happens.
Monitoring means comparing actual progress, cost and scope with the baseline from planning. Controlling means acting on what you see: approving or rejecting change requests, re-planning, or escalating a risk. Typical outputs are status reports and approved change requests. Without a baseline there is nothing to monitor against, which is why phases 2 and 4 depend on each other.
Phase 5: Closing
Hand over the result, get formal acceptance, release the team and record lessons learned. Many teams skip this phase because the work feels finished, and lose the lessons that would make the next project easier.
Closing includes handing over the final deliverable, getting the client's or sponsor's sign-off, releasing people and contracts, archiving documents and running a project retrospective: what went well, what did not, and what to do differently. The outputs are the sign-off, a final report and the retrospective notes.
How the phases overlap in real projects
The five phases are an order of logic, not five neat blocks on a calendar. In practice planning often starts before initiation is fully signed off, monitoring and controlling runs alongside execution from the first day of work, and closing tasks begin while the last deliverables are still being finished.
A typical shape: the phases overlap, but none is skipped.
Overlap is normal and often efficient. Skipping a phase is different: if the design is not solved before construction starts, or nobody tracks the budget against a baseline, the cost shows up later, usually as rework and delay.
The life cycle works with any method
The life cycle describes what a project goes through, not how the team works day to day. That "how" is the project management methodology. Waterfall is a sequential approach: the team finishes each stage (requirements, design, build, test, release) before starting the next, with scope agreed up front and one delivery at the end.
Agile is an iterative approach: the team delivers working pieces in short cycles, gets feedback after each one and adjusts the plan as it goes. Its values come from the 2001 Agile Manifesto. In agile projects, planning, execution, and monitoring and controlling repeat in every short cycle, while initiation and closing still happen once. So the five phases still apply; they are just arranged differently. You will compare the methods in Lesson 3: Project management methodologies and play the difference out in Lesson 4: Agile vs waterfall.
Case study: the Sydney Opera House, built before the design was solved
The Sydney Opera House is one of the most famous buildings in the world, and one of the clearest examples of what happens when execution starts before planning is finished. All facts below come from Kanbanchi's Great Projects page on the Sydney Opera House.
Great Projects case study
Sydney Opera House, 1957 to 1973
Buildings · Sydney, Australia
Initiation: a budget set to win approval
The estimate was about A$7 million and the building was to open on Australia Day, Jan 26, 1963. Premier Joe Cahill wanted work to start quickly, and Bent Flyvbjerg and colleagues describe the A$7 million figure as a political budget, set low to win approval before the elections.
Planning: the design was not solved
Jørn Utzon's winning competition entry was a set of sketches, not a buildable design. The site had not been properly surveyed either: it was assumed to be sandstone but turned out to be loose deposits saturated with seawater. When the ground was broken on Mar 2, 1959, only the start and the opening date were fixed, because the roof's weight and anchor points were still unknown.
Execution: building for loads nobody knew
About 700 concrete shafts had to be bored into the site, unbudgeted work. The podium was finished in February 1963, two years behind schedule, and still needed substantial modification to suit the final roof. Meanwhile Utzon and the engineers at Arup analyzed 12 trial schemes before settling on shells cut from a single sphere, presented in January 1962.
Monitoring and controlling: no baseline for the later stages
The Opera House had no published plan for its second and third stages, so, as the Kanbanchi page puts it, slippage only became visible when it was years long. After Utzon resigned in 1966, the team that replaced him found the interiors far less advanced than expected, and they were redesigned.
Closing
Queen Elizabeth II opened the building on Oct 20, 1973, at A$102 million, 1,357 percent over the original estimate and about ten years late.
What this shows about the life cycle
- Rushing initiation with a low, political estimate set expectations the project could never meet.
- Starting execution before planning was finished meant the podium was built, then modified, for a roof designed after it.
- Without a baseline for each stage, monitoring and controlling could not show the drift while it was still small.
Source: Sydney Opera House: planned vs actual cost and schedule, Kanbanchi Great Projects (data last updated Oct 25, 2026, with the original sources listed on that page).
Exercise: order the phases, then match the activities
Two quick steps. The phases start shuffled and the activities come from real projects: get instant feedback on each one.
Step 1: put the five phases in order
Drag the handles, or use the arrow buttons, to put the phases in the order a project moves through them. Then check your order.
Worked example
For a kitchen renovation, agreeing the goal and budget with the owner comes first (initiation), and the final walk-through and sign-off comes last (closing). Put all five phases in order below.
- 1Execution
- 2Initiation
- 3Closing
- 4Planning
- 5Monitoring and controlling
Step 2: match 10 activities to their phase
0 of 10 matched
Pick the phase where each activity belongs. You get feedback on every answer, and you can try again until it is right.
Worked example
"Write the weekly status report" belongs to Monitoring and controlling: status reports compare progress with the plan while the work happens. Now match the 10 activities below.
1. Write a project charter
Answer: Initiation. The charter is the main output of initiation: it names the goal, the sponsor and the main deliverables.
2. List the key stakeholders
Answer: Initiation. Identifying who is affected, or can affect the project, starts in initiation, next to the charter.
3. Hold a kickoff meeting with the whole team
Answer: Execution. In this course the kickoff launches the work once the plan is approved, so it marks the start of execution.
4. Break the work into tasks and estimate them
Answer: Planning. A work breakdown structure with estimates is core planning work.
5. Track the budget against the plan
Answer: Monitoring and controlling. Comparing actual cost with the baseline is monitoring and controlling.
6. Build the website pages the client asked for
Answer: Execution. Producing the deliverables is what execution is for.
7. Set the schedule and the budget
Answer: Planning. The schedule and budget become the baseline in the approved project plan.
8. Review and approve a change request
Answer: Monitoring and controlling. Deciding on changes against the plan is the controlling part of monitoring and controlling.
9. Hand over the final deliverable and get sign-off
Answer: Closing. Handover and formal acceptance close the project.
10. Run a project retrospective
Answer: Closing. The end-of-project retrospective records lessons learned, the last step of closing.
Knowledge check: Lesson 1
Five questions on this lesson. Get at least 4 right to complete Lesson 1 and move your course progress forward. Each answer comes with an explanation.
Key takeaways
- Every project moves through five phases: initiation, planning, execution, monitoring and controlling, and closing.
- Each phase has a job and an output: the charter, the approved plan, the deliverables, status reports and change decisions, and the final sign-off.
- Monitoring and controlling runs alongside execution and needs the baseline from planning.
- Phases can overlap, but skipping one, like starting to build before the design is solved, comes back as rework and delay.
Try it on a real board: a life cycle board in Kanbanchi
Want to see the phases on your own project? Set up a board in Kanbanchi, the task and project management app that works inside Google Workspace, in a few minutes:
- Create a new board and name it after your project.
- Add five lists: Initiation, Planning, Execution, Monitoring and controlling, Closing.
- Add a card for each activity from the exercise above, such as "Write a project charter", and drop it into its phase.
- Give the cards start and due dates and assignees, then switch to the Gantt chart view to see the phases as a timeline.
- Move cards as work progresses, and keep the retrospective card in Closing so it is not forgotten.
This step is optional. The course works without an account, and your progress does not depend on it.
Project life cycle: FAQ
What are the 5 phases of the project life cycle?
The five phases are initiation, planning, execution, monitoring and controlling, and closing. Initiation sets the goal, planning works out how to reach it, execution does the work, monitoring and controlling keeps it on track, and closing hands over the result and records lessons learned.
Can project phases overlap?
Yes. Planning often starts before initiation is fully signed off, monitoring and controlling runs alongside execution, and closing tasks start while the last work is finishing. Overlap is normal; skipping a phase is what causes rework and delay.
Do agile projects have a project life cycle?
Yes. Agile projects still start, run and finish. In agile projects, planning, execution, and monitoring and controlling repeat in every short cycle, while initiation and closing still happen once.
What is the difference between the project life cycle and project management phases?
In everyday use they mean the same thing: the project management phases are the stages of the project life cycle. Some industries add their own stage names, such as design or testing, inside execution, but the five phases stay the same.