The 311 citizen-request intake team sees tickets arrive in bursts after storms, making two-week iteration planning feel like theater. What method choice should the SM/TC consider?
Select an answer to reveal the explanation.
Short Explanation
Storm-week 311 is a fire hose, not a garden watering schedule. Pretending you can Sprint-plan the next downpour is theater. Team Kanban lets the crew pull what arrived — and they still ride the ART's cadence.
Full Explanation
When 311 citizen-request intake sees tickets arrive in bursts after storms, the SM/TC should consider SAFe Team Kanban for uneven arrival of work while staying on the ART cadence. Storm-week 311 is a fire hose, not a garden watering schedule; Team Kanban lets the crew pull what arrived without pretending the next downpour is already known. The team still rides the ART's iteration and PI drumbeat.
Dropping the ART cadence so the team plans only when storms hit fails because method fit is not a hall pass out of the train. Forcing a two-week Sprint Goal that pretends the storm queue is already known fails because fake goals over unknown volume are planning theater. Moving 311 intake off the ART as a standalone help desk fails because leaving the train abandons System Demo, PI events, and cross-team alignment without solving arrival pattern.
Exam caveat: Team Kanban addresses arrival pattern inside SAFe; it does not mean abandoning cadence. Operational check: visualize 311 arrival and WIP, trial Team Kanban policies while keeping ART events, compare flow during storm bursts, and keep fake Sprint Goals from substituting for pull-based management of intake. Keeping 311 on the ART while changing the team method preserves System Demo transparency and PI dependency management that a standalone help desk would lose.