Skip to content
PMPCAPM

Adaptive Life Cycle

An adaptive life cycle is a change-driven approach that is both iterative and incremental, where the detailed scope is defined and approved before the start of each iteration.

Share:

Know it well enough for the exam? Questions on Adaptive Life Cycle are scenario-based, not definitional.

Practice it free

Explanation

Adaptive life cycles — often called agile — are designed for environments with high levels of change and uncertainty. Rather than attempting to define the full scope upfront, the team works in short iterations (typically one to four weeks), with the scope for each iteration determined just before it begins. This allows the project to respond to changing requirements, stakeholder feedback, and emerging information.

Agile methods such as Scrum, Kanban, and Extreme Programming (XP) are implementations of the adaptive life cycle. They emphasize customer collaboration, working software (or deliverables) over comprehensive documentation, responding to change over following a plan, and individuals and interactions over processes and tools — the four values of the Agile Manifesto.

Adaptive life cycles work best when requirements are uncertain or rapidly evolving, when the customer wants frequent delivery of value, and when the team can work in close collaboration with stakeholders. They require a high degree of stakeholder involvement, empowered teams, and organizational support for iterative decision-making.

Key Points

  • •Change-driven, combining iterative and incremental approaches
  • •Detailed scope is defined at the start of each iteration, not upfront
  • •Emphasizes customer collaboration and rapid feedback loops
  • •Requires empowered teams and active stakeholder engagement

Exam Tip

PMI views agile as one end of a spectrum, not a separate discipline. If a scenario describes evolving requirements, short iterations, and close customer collaboration, it points to an adaptive life cycle.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Predictive Life Cycle (Waterfall)

A predictive life cycle is a plan-driven approach where the project scope, schedule, and cost are determined early and changes are carefully managed.

Subsidiary Plans

Subsidiary plans are the individual management plans that are components of the overall project management plan, each addressing a specific Knowledge Area or management function.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Critical Path Method (CPM)

The Critical Path Method (CPM) is a schedule network analysis technique that calculates early and late start and finish dates for every activity to find the longest path through the project, the minimum project duration, and the float on every other path.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Part of

PM Fundamentals & Frameworks

Study full domain →

Practice Adaptive Life Cycle

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.