Which statement is true about Iteration planning for Kanban teams?

Question

Options

• AKanban teams estimate their velocity
• BKanban teams publish Iteration goals
• CKanban teams do not commit to service level agreements
• DKanban teams find high value in trying to plan the Iteration in detail

• A
  3% (1)
• B
  94% (29)
• D
  3% (1)

Explanation

Kanban teams in SAFe still participate in Iteration planning and publish Iteration goals to stay aligned with the Agile Release Train (ART), even though their planning approach differs from Scrum teams - they don't commit to a fixed iteration backlog, but they do communicate intent and priorities through goals.

Why the distractors are wrong:

• A is wrong because Kanban teams use flow metrics (throughput, cycle time, WIP limits) rather than velocity, which is a Scrum concept tied to time-boxed sprints.
• C is wrong because Kanban teams do commit to Service Level Expectations (SLEs) - defining how long items should spend in each workflow state is a core Kanban practice.
• D is wrong because detailed Iteration planning contradicts Kanban's pull-based, flow-driven approach; that level of upfront planning is characteristic of Scrum, not Kanban.

Memory tip: Think of Kanban teams as "goalful but flexible" - they share goals (alignment with the ART) but skip the detailed commitments (no sprint backlog, no velocity). The keyword in option B is "publish," which is a lightweight, flow-friendly action that fits Kanban perfectly.

No community discussion yet for this question.