CAPM Practice: Explain when it is appropriate to use an adaptive approach

The Agile Manifesto's fourth principle states: 'Responding to change over following a plan.' Adaptive approaches embrace change as a natural part of project work, providing structured mechanisms (iterations, reviews, retrospectives) to incorporate new learning. This is the fundamental philosophical difference from predictive methods.

**Why not A:** Comprehensive upfront planning before starting is the hallmark of predictive (waterfall) project management. Adaptive approaches deliberately avoid extensive upfront planning, instead planning iteratively as the project progresses and more information becomes available.

**Why not B:** Requiring formal specification documents before development begins is a predictive practice. Adaptive approaches use lightweight artifacts like user stories and acceptance criteria that evolve throughout the project, not comprehensive specifications locked before work starts.

**Why not C:** Delivering the entire product only at project completion is a big-bang delivery approach. Adaptive project management delivers working increments iteratively, providing value early and frequently rather than waiting until the end.