After choosing SAFe Team Kanban, parks volunteer-management staff ask to skip System Demo because Kanban teams do not demo on a cadence. What should the SM/TC do?
Select an answer to reveal the explanation.
Short Explanation
Kanban is a team method, not a hall pass out of the train. Parks still rides the ART, so System Demo, PI Planning, and Inspect and Adapt stay on the calendar. Switching the board style does not switch off cadence.
Full Explanation
Parks or other Team Kanban groups still participate in the ART: the SM/TC coaches that Kanban is a team method, not a hall pass out of System Demo, PI Planning, or Inspect and Adapt. Continuous pull coexists with train synchronization so enabling and feature work stay aligned for public parks services. Method choice never opts the team out of SAFe cadence obligations.
Skipping System Demo because flow should never be interrupted fails because demo is how the ART inspects integrated value. Skipping PI Planning because Kanban teams "do not plan" fails because SAFe Kanban teams still plan on the PI cadence even as they pull continuously. Treating IP iteration events as optional for Kanban teams fails because improvement and innovation time remains part of the train rhythm.
Exam caveat: continuous flow is inside the ART drumbeat, not instead of it. Operational check: keep parks Kanban policies for daily pull, put System Demo and PI events on the calendar as non-negotiable, refine Team PI Objectives, and correct any narrative that Kanban equals leaving the train. Parks enabling work that skips ART demos leaves feature teams guessing about platform readiness residents will eventually notice.