Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 41 Β· Initiation and Planning

The Project Life Cycle and Phases

Learn the phases of the project management life cycle, how phase gates work, and how predictive, iterative and agile life cycles differ, with examples and a small phase tracker.

Every project passes through a sequence of phases from the moment someone has the idea until the result is delivered and the team disbands. That sequence is the project life cycle. It gives the work a shape, so everyone can see where they are and what must happen before moving on.

Do not confuse it with the five process groups from What Is Project Management?. Process groups describe kinds of activity that recur through the project. The life cycle describes the phases in time.

The generic life cycle

Most projects share this pattern:

  1. Starting: the idea is assessed, goals are set and authorization is given.
  2. Organizing and preparing: planning, assembling the team, approving the baseline.
  3. Carrying out the work: building, testing, installing.
  4. Closing: acceptance, handover, lessons learned.

Effort and cost start low, rise during execution and fall at closing. Risk and the ability to change things are highest early and shrink over time, while the cost of making a change grows. This is why early planning and clear requirements are so valuable.

flowchart LR
    A[Starting] --> B[Planning and preparing]
    B --> C[Executing the work]
    C --> D[Closing]
    G1{{Gate 1}} -.-> A
    G2{{Gate 2}} -.-> B
    G3{{Gate 3}} -.-> C

Gates are decision points between phases: continue, change or stop.

Phase gates

A phase gate (or stage gate) is a review at the end of a phase. The sponsor or steering group checks: Were the deliverables produced? Are cost and schedule on track? Is the business case still valid? Is the next phase ready? The result is go, go with changes, hold or stop. Gates keep a failing project from consuming money for months.

Life cycle types

Type Idea Best when
Predictive (waterfall) Plan everything first, then deliver in sequence Requirements are stable and well understood; construction, regulated work
Iterative Repeat cycles that refine the product, with scope agreed at the start The product needs several refinements; scope understood but details are not
Incremental Deliver finished slices of the product over time Early partial value is useful
Adaptive (agile) Short cycles, scope changes between cycles Requirements change and feedback matters
Hybrid Combine, such as a predictive plan with agile delivery Large organizations with fixed budgets and uncertain details

A software example

A website project might look like this under a predictive cycle:

Phase Output
Initiation Charter, sponsor approval
Requirements Requirements document
Design Wireframes, architecture
Build Working site
Test Test report
Deploy Live site and training
Close Lessons learned

In an adaptive cycle the same project would deliver a small working version every two weeks, with the order of features revisited each time.

Choosing a life cycle

Predictive Stable needs, plan first
Iterative Refine in cycles
Incremental Deliver in slices
Adaptive Change welcome

Fit the cycle to how clear the requirements are.

1 / 2

Tracking phases in code

A tiny tracker can enforce the gate idea: you cannot move forward until the gate criteria hold.

Python A phase gate checker

Press Run (or Ctrl + Enter) to see the result here.

Program input Β· what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Cost of change over time

Python Why early changes are cheap

Press Run (or Ctrl + Enter) to see the result here.

Program input Β· what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The numbers are only illustrative, but the shape (cheap early, expensive late) holds for predictive projects. Adaptive life cycles try to flatten the curve by getting feedback sooner.

Product life cycle versus project life cycle

A product lives longer than the project that creates it: concept, development, introduction, growth, maturity, retirement. The project covers only part of that. Remember that after delivery, the product enters operations, and projects may repeat later to upgrade or retire it.

Check your understanding

Quick check Β· 4 questions

of 4 answered You scored / 4 Β· perfect!

  1. 1. What is a phase gate?

    Gates are decision points between phases.
  2. 2. When is the cost of change usually lowest in a predictive project?

    Changes made early affect fewer finished items, so they cost less.
  3. 3. Which life cycle fits rapidly changing requirements best?

    Adaptive cycles welcome change between short iterations.
  4. 4. How do process groups differ from life cycle phases?

    Processes repeat in every phase; phases describe the timeline.

Summary

  • The life cycle is the sequence of phases from start to close; phase gates control progress.
  • Predictive, iterative, incremental, adaptive and hybrid life cycles suit different levels of uncertainty.
  • Risk and flexibility fall over time while the cost of change rises.
  • Choose the life cycle that matches how well the requirements are known.

Next: Business Case and Project Charter