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

A Kanban board visualizes work flow through columns representing workflow states (e.g., To Do, In Progress, Done). Work-in-progress (WIP) limits on each column prevent bottlenecks and ensure smooth flow. Teams use the visual representation to identify bottlenecks, manage flow, and prioritize work without time-boxed sprints — Kanban is pull-based rather than sprint-based.

**Why not A:** Budget and cost variance tracking are financial management activities that belong in earned value reports or cost management tools — not on a Kanban board. A Kanban board visualizes work items and flow states; it contains no financial data and is not designed for cost performance measurement.

**Why not B:** Retrospective action items may occasionally be captured as work items on a task board, but documenting retrospective outcomes is not the fundamental purpose of a Kanban board. Retrospective outputs are typically tracked in a separate artifact; the Kanban board's defining purpose is continuous flow visualization and WIP management.

**Why not D:** Sprint planning and story point assignment are Scrum practices tied to the time-boxed sprint model. Kanban is explicitly not sprint-based — it uses a continuous flow model with WIP limits rather than fixed iterations. Applying sprint-specific concepts to Kanban conflates two distinct agile frameworks with meaningfully different operating models and principles.