Project Life Cycle

The ordered progression of phases a project moves through, from its beginning to its end.

Key Points

  • Structures the project into distinct phases that may be sequential or overlapping.
  • Phase names and counts vary by organization and industry (e.g., concept, planning, execution, closure).
  • Includes governance checkpoints (phase gates) for go/no-go or continue decisions between phases.
  • Different from process groups; the process groups can repeat within each life cycle phase.

Example

An engineering firm uses a four-phase life cycle: concept, design, build, and closeout. After design, a phase-gate review checks drawings, budget, and risks to authorize moving into construction.

PMP Example Question

Which statement best describes the project life cycle?

  1. A set of related phases that take a project from beginning to end.
  2. The five process groups: Initiating, Planning, Executing, Monitoring and Controlling, and Closing.
  3. The sequence of stages a product goes through from market launch to retirement.
  4. The organizational methodology used to manage portfolios.

Correct Answer: A — Project life cycle

Explanation: The project life cycle is the structured series of project phases; process groups (B) repeat within phases, product life cycle (C) concerns the product, and (D) relates to portfolio management.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course