A new permits-plan-review feature team has a relatively stable Feature backlog and benefits from iteration goals, but a director says they should “upgrade” to Kanban because it is more advanced. What should the SM/TC coach?
Select an answer to reveal the explanation.
Short Explanation
Kanban is not a black belt you award after Scrum. A permits feature team with a stable backlog and useful iteration goals is already in a good SAFe Scrum neighborhood. Upgrade talk is prestige, not flow.
Full Explanation
Many ART teams reasonably use SAFe Scrum when they can plan a coherent iteration goal against a relatively stable Feature backlog. Team Kanban is chosen for context — uneven arrival, interrupt-driven operations — not as a maturity promotion. Switching for optics, treating Kanban as a penalty after a miss, or alternating methods every iteration all ignore fit. The SM/TC coaches method as a flow decision.