Adaptive Project Life Cycle: Flexible Scheduling with Timeboxed Iterations

PMBOK v8 Definition

The adaptive project life cycle is a development approach where schedules are more flexible, and the project is divided into sprints or iterations with short-term planning horizons. Tailoring in adaptive projects involves creating timeboxed schedules that can adapt to changes in the project scope and priorities. This approach sits on one end of the development spectrum, opposite the predictive life cycle.

Why It Matters for the Exam

The adaptive life cycle appears frequently in PMI exam questions testing your ability to distinguish between predictive, adaptive, and hybrid approaches. Questions often present a scenario requiring you to identify when adaptive scheduling is appropriate or to select the correct tailoring technique for flexible scope environments.

Key Points to Remember (for the exam)

• Core Structure: Project divided into sprints or iterations with short-term planning horizons
• Scheduling Flexibility: Schedules are more flexible compared to predictive approaches
• Tailoring Technique: Creating timeboxed schedules that adapt to changes in scope and priorities
• Development Spectrum: Adaptive is on one end; predictive is on the opposite end; hybrid sits between them
• Change Management: Changes are expected and accommodated within each iteration, not through formal change control
• Planning Horizon: Detailed planning occurs only for the next iteration, not the entire project upfront
• Common Confusion: Adaptive does NOT mean "no schedule"—it means timeboxed, iterative scheduling

Typical PMI Exam Example

A software development project has unclear requirements that are expected to evolve. The project manager divides work into two-week sprints, planning only the next sprint in detail. When stakeholders request new features, the team adjusts the next sprint backlog accordingly. This is an adaptive life cycle using timeboxed schedules.

PMI Exam Traps

• Trap: Thinking adaptive means "no planning at all"

• Reality: Adaptive projects plan iteratively with short-term horizons, not upfront

• Trap: Confusing adaptive with "no schedule baseline"

• Reality: Each iteration has a timeboxed schedule baseline that can change between iterations

• Trap: Assuming adaptive is always better than predictive

• Reality: Adaptive is appropriate when scope is uncertain; predictive works when requirements are stable

• Trap: Believing hybrid is just "adaptive plus predictive" in equal parts

• Reality: Hybrid combines both approaches in various patterns (e.g., predictive upfront with adaptive streams, or adaptive development with predictive rollout)

Important PMI Connections

Quick Review Questions

1. In an adaptive life cycle, what is the primary tailoring technique for scheduling?

2. A project manager divides work into four-week iterations with detailed planning only for the next iteration. Which life cycle is being used?

3. True or False: In adaptive projects, changes to the schedule baseline require formal change management procedures.

4. A construction project with IT integration uses predictive methods for building and adaptive methods for software development. What development approach is this?

5. On the development spectrum, where does the adaptive approach sit in relation to predictive and hybrid approaches?

PMBOK v8 Reference

Section 4.3 - Development Approach and Life Cycle (including predictive, adaptive, and hybrid methods)