A municipal call-center tooling team wants Kanban rather than Scrum. Which components correctly describe Kanban at CAPM depth?
Select an answer to reveal the explanation.
Short Explanation
Kanban’s core pitch is see the work, cap how much is open, and keep it moving. No rule says you must run Scrum sprints to do that. Flow first; timeboxes are optional add-ons, not the definition.
Full Explanation
Kanban components center on visualizing work, limiting work in progress, and managing flow. Unlike Scrum, Kanban does not require timeboxed sprints, Sprint Goals, or Scrum accountabilities. CAPM-level distinction is flow-based control versus Scrum’s prescribed events and roles.