SkarpSkarp

Chapter 2 of 21

Projects, Operations, and Life Cycles: Foundations for CAPM

Before you tackle formulas or frameworks, you need rock‑solid clarity on what a project is, how it differs from operations, and how different life cycles shape everything else you’ll learn.

27 min readen

Step 1 – Why Projects vs Operations Matter for CAPM

Exam Stories, Not Just Formulas

CAPM questions often start with short scenarios: a hospital upgrade, an app launch, a factory line. To answer, you must spot: is this a project or operations, and what life cycle is being used?

Where This Module Fits

This module lives in Project Management Fundamentals and Core Concepts and connects directly into Predictive (Plan-Based) Methodologies and Agile Frameworks and Methodologies on the CAPM exam.

Why Misclassification Hurts

If you mislabel operations as a project, or choose the wrong life cycle, you will likely pick the wrong next action, misunderstand governance, and engage the wrong stakeholders at the wrong time.

Your Learning Targets

You will master the PMI project definition, distinguish projects from operations, contrast project and product life cycles, and compare predictive, adaptive, and hybrid approaches with real scenarios.

Step 2 – Canonical PMI Definition of a Project

Memorize This Definition

For CAPM you must know: project: "A temporary endeavor undertaken to create a unique product, service, or result." Learn it exactly; many questions assume this wording.

Temporary and Endeavor

Temporary means there is a start and an end. Endeavor means a coordinated effort of people and resources, not just scattered tasks.

Unique Outcome

Projects create a unique product, service, or result. Even repeated builds, like similar houses, are unique due to location, timing, and stakeholders.

Common Traps

Monthly financial close or ongoing customer support are operations, not projects, because they are repetitive and do not have a defined end.

Borderline Case

Designing and rolling out a new quarterly reporting process is a project. Running that report every quarter afterward is operations.

Step 3 – Projects vs Operations vs Programs vs Portfolios

Projects vs Operations

Projects are temporary and unique. Operations are ongoing and repetitive, focused on efficiency and stability, like daily transaction processing or routine maintenance.

What Is a Program?

A program is a group of related projects, and sometimes operations, managed together for benefits you would not get managing them separately.

Program Example

A hospital’s Digital Transformation Program: EHR project, patient app project, analytics project, plus training and support operations coordinated together.

What Is a Portfolio?

A portfolio is a collection of projects, programs, and sometimes operations managed together to achieve strategic objectives, like a Healthcare Solutions Portfolio.

Nested Boxes Picture

Visualize small project boxes grouped into a program box; multiple program and project boxes sit inside a bigger portfolio box, with operations running continuously underneath.

Step 4 – Project Life Cycle vs Product Life Cycle

Project Life Cycle

A project life cycle is the series of phases a project passes through from start to finish: initiating, planning, executing, monitoring and controlling, and closing.

Product Life Cycle

A product life cycle is the stages a product or service goes through in the market: introduction, growth, maturity, decline, and retirement.

Different Questions

Project life cycle asks: how does this project progress from idea to closure? Product life cycle asks: how does this product exist and evolve over its lifetime?

Many Projects per Product

One product life cycle can include many projects: initial development, new-country launches, major feature upgrades, and redesigns.

Exam Trap

Continuous updates over many years describe the product life cycle. Each major update or release is still a temporary project within that longer product life.

Step 5 – Predictive and Adaptive Life Cycles (Canonical Definitions)

Predictive Life Cycle Definition

Predictive life cycle: "A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle."

Adaptive Life Cycle Definition

Adaptive life cycle: "A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration."

Predictive in Practice

Predictive suits stable, well-understood requirements, with detailed up-front planning and tight formal change control, like building a bridge.

Adaptive in Practice

Adaptive suits changing or unclear requirements, using short iterations with fixed time and cost but flexible detailed scope, like a new mobile app.

Development vs Project Life Cycle

Predictive and adaptive are development life cycles used inside the broader project life cycle; one project can mix them for different components.

Step 6 – Predictive vs Adaptive vs Hybrid Approaches

Predictive Approach

Predictive uses a predictive life cycle. It fits stable, well-known requirements, with detailed up-front plans and strict change control, often to satisfy fixed-scope contracts.

Adaptive Approach

Adaptive uses agile, iterative, or incremental life cycles. It fits high uncertainty, emerging requirements, and frequent stakeholder feedback with detailed planning per iteration.

Hybrid Approach

Hybrid combines predictive and adaptive. Stable, regulated parts may be predictive; innovative or user-facing parts are handled adaptively in iterations.

Key Choice Factors

Choose based on requirements stability, level of uncertainty, stakeholder availability for feedback, and governance needs such as fixed baselines or regulatory demands.

Exam Reading Strategy

When reading a scenario, highlight clues about how clear requirements are, how often stakeholders can engage, and how strict governance is. Match those clues to the right approach.

Step 7 – Scenario Walkthroughs: Choosing the Right Approach

Scenario A: Highway Extension

Highway project with stable standards, strict regulations, and formal change approval. Best fit: predictive, with detailed up-front planning and fixed baselines.

Scenario B: Social Media App

Vision is clear but user preferences are unknown; team wants 2-week cycles and constant feedback. Best fit: adaptive, using agile iterations.

Scenario C: Bank Core and App

Regulated, stable core system plus exploratory mobile app. Core: predictive. App: adaptive. Overall: hybrid approach mixing both.

Pattern Recognition

Stable requirements and strict governance point to predictive. Uncertain, evolving requirements with frequent feedback point to adaptive. Mixed conditions suggest hybrid.

Step 8 – Life Cycle Choice, Planning Detail, and Change Management

Planning in Predictive

Predictive approaches front-load planning: detailed scope, schedule, and cost baselines plus risk, quality, and resource plans are created early.

Planning in Adaptive

Adaptive approaches keep a high-level roadmap but do detailed planning just in time before or during each iteration, focusing on the next slice of work.

Change in Predictive

In predictive, change is controlled via formal mechanisms like change control boards; changes are exceptions that may alter baselines.

Change in Adaptive

In adaptive, change is expected. New ideas enter the product backlog and are reprioritized; iterations are time-boxed to keep control.

Exam Clues

Strict baselines and formal approvals point to predictive. Frequent reprioritization and welcoming change point to adaptive approaches.

Step 9 – Life Cycles, Governance, and Stakeholder Engagement

Phase Gates and CCBs

Predictive projects use phase gates at the end of major phases and change control boards to review and approve changes before they affect baselines.

Adaptive Governance

Adaptive approaches rely on iteration reviews and retrospectives as lightweight governance, making funding and scope decisions incrementally.

Stakeholder Definition

Stakeholder: "An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio."

Engagement in Predictive

In predictive, stakeholders are deeply involved early for requirements and design, then mainly at milestones and phase gates.

Engagement in Adaptive

In adaptive, key stakeholders such as the product owner and customers engage continuously, reviewing increments every iteration.

Step 10 – Thought Exercise: Classify and Justify

Work through this exercise to solidify distinctions. For each situation, decide:

  1. Is it a project or operations?
  2. If it is a project, which approach fits best: predictive, adaptive, or hybrid?

Write your answers in a notebook or mentally walk through them, then compare with the suggested reasoning.

---

  1. Scenario 1: University Course Delivery
  • A university runs the same "Intro to Economics" course every semester. The syllabus changes slightly every few years, but each semester follows a standard schedule and assessments.

Questions:

  • Project or operations?
  • If a project, which approach?

Suggested reasoning:

  • This is operations: ongoing, repetitive work with no defined end date.
  • A project might exist to redesign the course or move it online; that separate initiative could use a predictive or hybrid approach depending on how fixed the requirements are.

---

  1. Scenario 2: Campus-Wide Wi-Fi Upgrade
  • The university decides to replace all Wi-Fi equipment across campus within 12 months to meet new security standards. Requirements are clear. There is a fixed budget and strict deadline before the next academic year.

Questions:

  • Project or operations?
  • Which approach?

Suggested reasoning:

  • This is a project: temporary, with a clear end and a unique result (upgraded Wi-Fi infrastructure).
  • Best fit: predictive. Requirements and standards are clear, and governance favors fixed scope, cost, and schedule.

---

  1. Scenario 3: Experimental Student App
  • A small team wants to create an app to help students find study partners. They are unsure which matching features will work and plan to test ideas with students every two weeks.

Questions:

  • Project or operations?
  • Which approach?

Suggested reasoning:

  • This is a project: temporary effort to create a unique app.
  • Best fit: adaptive. Requirements are uncertain, feedback cycles are short, and the team expects to pivot based on student input.

Use this pattern on the CAPM exam: classify first (project vs operations), then choose the life cycle/approach.

Step 11 – Quick Check: Definitions and Distinctions

Test your understanding of core definitions and distinctions before moving on.

Which statement best matches a predictive life cycle in the context of a project?

  1. A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
  2. A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
  3. Any life cycle that combines both projects and operations to maximize value delivery.
  4. A process where operations teams plan and execute repetitive tasks with minimal change.
Show Answer

Answer: A) A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.

The canonical definition of a predictive life cycle is: "A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle." Option 2 is the canonical definition of an adaptive life cycle. Options 3 and 4 describe other ideas but not the PMI definition of a predictive life cycle.

Step 12 – Scenario Quiz: Choose the Approach

Apply what you have learned to a short scenario.

A medical device company must update its software to comply with a new regulation that is fully specified. At the same time, it wants to experiment with new optional features based on doctor feedback. Regulators require a detailed plan and fixed deadlines for the compliance part, but the innovation features can evolve. What is the MOST appropriate overall approach?

  1. Fully predictive approach for all work
  2. Fully adaptive approach for all work
  3. Hybrid approach combining predictive for compliance and adaptive for new features
  4. Operations, because the company is just maintaining an existing product
Show Answer

Answer: C) Hybrid approach combining predictive for compliance and adaptive for new features

Compliance work has stable, fully specified requirements and strict governance, which suits a predictive approach. Innovation features are uncertain and benefit from frequent feedback, which suits an adaptive approach. Combining them makes this a hybrid approach. It is not pure operations because the changes are a temporary endeavor to create a unique result.

Step 13 – Flashcard Review: Core Terms

Use these flashcards to reinforce the key definitions that the CAPM exam expects you to know exactly.

Project (PMI canonical definition)
A temporary endeavor undertaken to create a unique product, service, or result.
Stakeholder (PMI canonical definition)
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
Predictive life cycle (PMI canonical definition)
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
Adaptive life cycle (PMI canonical definition)
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
Project life cycle vs product life cycle
Project life cycle: phases a project goes through from start to finish. Product life cycle: stages a product or service goes through in the market from introduction to retirement.
Predictive approach
Project management approach that relies mainly on a predictive life cycle, with detailed up-front planning and tight change control, suited to stable requirements and strict governance.
Adaptive approach
Project management approach that relies on adaptive (agile/iterative/incremental) life cycles, with short iterations and evolving scope, suited to high uncertainty and frequent feedback.
Hybrid approach
Approach that combines predictive and adaptive elements, often using predictive for stable, regulated components and adaptive for innovative or uncertain components.
Phase gate (stage gate)
A governance review at the end of a project phase where a decision is made to continue, modify, or terminate the project or phase.
Change control board (CCB)
A formally chartered group responsible for reviewing, evaluating, approving, delaying, or rejecting changes to the project, and for recording and communicating such decisions.

Key Terms

program
A group of related projects, and sometimes operations, managed in a coordinated way to obtain benefits not available from managing them individually.
project
A temporary endeavor undertaken to create a unique product, service, or result.
portfolio
A collection of projects, programs, and sometimes operations managed as a group to achieve strategic objectives.
operations
Ongoing, repetitive activities that produce the same product or service and sustain the business, without a defined end date.
phase gate
A review at the end of a phase where governance bodies decide whether to continue, modify, or terminate the project or phase.
stakeholder
An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
hybrid approach
A project management approach that combines predictive and adaptive elements to match different parts of the work to their uncertainty and governance needs.
adaptive approach
A project management approach that uses adaptive (agile, iterative, or incremental) life cycles with short iterations and evolving scope, suited to high uncertainty.
product life cycle
The stages a product or service goes through from introduction through growth and maturity to decline and retirement.
project life cycle
The series of phases that a project passes through from its start to its completion.
adaptive life cycle
A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
predictive approach
A project management approach that uses a predictive life cycle with detailed up-front planning and strict change control, suited to stable requirements.
change control board
A formally designated group that reviews and decides on proposed changes to the project scope, schedule, or cost baselines.
predictive life cycle
A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.

Finished reading?

Test your understanding with a custom practice exam on this chapter.

Test yourself