CAPM Practice: Explain the components of an adaptive plan

Adaptive planning is structured and deliberate, not chaotic. It includes: sprint planning (2-4 hours per sprint), release planning (multi-sprint), backlog refinement (ongoing), velocity measurement, and burndown/burnup tracking. What differs from predictive planning is: shorter cycle lengths (sprints vs. phases), deliberate uncertainty management through iteration, and planned flexibility built into the process. 'Adaptive planning' is not 'no planning.'

**Why not A:** Adaptive projects absolutely have defined goals and objectives — a clear product vision and prioritized backlog are prerequisites for adaptive planning to work at all. What differs from predictive approaches is how and when detailed plans are elaborated, not whether goals exist.

**Why not B:** Adaptive planning is not a synonym for undocumented work. Agile teams produce numerous artifacts: product backlog, sprint backlog, definition of done, velocity charts, burndown charts, and retrospective action items. Documentation is lean and just-enough, not absent.

**Why not D:** Adaptive projects generate many artifacts, including the product backlog, sprint backlog, definition of done, burndown/burnup charts, and increment review outputs. The distinction from predictive projects is that documentation is kept proportionate and working software is prioritized — not that artifacts are eliminated entirely.