Components of an Adaptive Plan

CAPM expects a working-level map of the most common adaptive frameworks, not deep mastery of any one of them. Scrum structures work into fixed-length sprints with defined roles (a Scrum Master, a Product Owner, and the Developers) and a small set of named events (Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective). Extreme Programming (XP) shares Scrum's iterative spirit but adds engineering-specific practices — pair programming, test-driven development, continuous integration — aimed specifically at technical quality.

Kanban visualizes work as it flows across a board (commonly To Do, In Progress, Done) and limits how much work can be "in progress" at once (a work-in-progress or WIP limit), pulling new work in only as capacity frees up, rather than working in fixed-length iterations at all. The Scaled Agile Framework (SAFe) exists to coordinate many agile teams working on one larger program or portfolio at once — it's less a single team's day-to-day method and more a structure for keeping dozens of Scrum- or Kanban-style teams aligned toward the same larger goal.

Study focus: a question naming "a strict WIP limit and a continuous flow of work, with no fixed-length iterations" is describing Kanban, not Scrum — the exam tests recognizing a framework from its described characteristics, so knowing each one's one or two signature features is more useful than memorizing every detail.