Challenge Your Exam Readiness With Our Free CAPM Practice Questions

The CAPM agile domain expects candidates to select frameworks based on context. Kanban is well-suited to environments with variable incoming work, such as operations and support, because it emphasizes workflow visualization, explicit work-in-progress (WIP) limits, pull-based scheduling, and continuous delivery. These practices reveal bottlenecks, stabilize flow, and reduce cycle time through incremental improvements. Scrum (Option A) organizes work into timeboxed sprints with fixed goals; it’s powerful for product development but less optimal when arrival rates are unpredictable and items must be addressed as they come. Extreme Programming (Option C) offers valuable engineering practices but does not, by itself, provide a flow-based system for variable demand. Hybrid stage-gated approaches (Option D) reintroduce fixed phases and queueing that can exacerbate wait times. Implementing Kanban begins with mapping the workflow, setting initial WIP limits per column, measuring lead and cycle time, and using cadence-based reviews (e.g., replenishment, operations reviews) to tune policies. This complements service-level expectations and fosters transparency and continuous improvement, aligning tightly with agile principles of flow and value delivery.