Life Cycle

The life cycle is the structured path a project follows from beginning to end, divided into defined phases with deliverables and reviews that guide planning, control, and go/no-go decisions.

Key Points

  • Organizes the project into sequential or overlapping phases from start through closure, providing a management framework.
  • Each phase typically ends with a review or gate to continue, redirect, or terminate the work.
  • Phase names, counts, and details are tailored by the organization and may be predictive, iterative, incremental, or hybrid.
  • Also called "project life cycle" (See project life cycle.); not the same as the product life cycle or the PM process groups.

Example

A city bridge project uses Concept, Design, Procurement, Construction, and Commissioning phases. After Design, a gate review confirms scope, budget, and risks before funding Construction.

PMP Example Question

Which statement best describes a project's life cycle?

  1. The sequence of phases a project goes through from start to finish, often with decision gates between phases.
  2. The five process groups used to manage work throughout the project.
  3. The period from a product's market launch through retirement.
  4. The time-phased list of tasks that makes up the project schedule.

Correct Answer: A — The project's phased life cycle

Explanation: The life cycle defines the project's phases from beginning to end. The other options describe process groups, product life cycle, or a schedule.

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


Launch your Agile career!

HK School of Management helps you learn Agile and Scrum with practical playbooks, AI-powered prompts, and real-world workflows for planning and delivery. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More