The wastewater System Team wants to abandon the ART iteration cadence because they chose Kanban. What should the SM/TC remind them?
Select an answer to reveal the explanation.
Short Explanation
Choosing Kanban is not a hall pass out of the wastewater ART. The team can pull continuously and still show up on the same iteration drumbeat as everyone else. Cadence is how the train stays a train.
Full Explanation
A wastewater System Team that wants to abandon ART iteration cadence because it chose Kanban must be reminded that SAFe Team Kanban still operates on the ART iteration and PI cadence. Choosing Kanban is not a hall pass out of the train: the team can pull continuously and still show up for planning, System Demo, and PI events. Cadence is how the ART stays a train.
Claiming Kanban teams plan only when WIP hits zero so cadence is optional fails because SAFe does not make cadence optional for Team Kanban. Saying System Teams sit outside the ART and can ignore PI events fails because System Teams are on the train, not beside it. Dropping System Demo so Kanban flow is never interrupted fails because demo and inspect-and-adapt obligations remain.
Exam caveat: continuous pull coexists with synchronized ART events; method choice is not opt-out from SAFe. Operational check: keep the wastewater System Team on ART cadence events, let them pull work with Kanban policies between those events, attend System Demo, and correct any narrative that Kanban equals leaving the train. Wastewater System Teams especially need ART cadence because their enabling work must synchronize with feature teams that depend on platform readiness.