The vital-records team is high-performing in Scrum, and a director wants Kanban “because SASM said Kanban is advanced.” What should the SM/TC recommend?
Select an answer to reveal the explanation.
Short Explanation
If vital records is already humming in Scrum, swapping to Kanban for a certificate brag is like replacing a working copier because the catalog called another one 'advanced.' Fit beats prestige. Leave the team on Scrum until the work itself changes.
Full Explanation
If a vital-records team is already high-performing in Scrum, the SM/TC should recommend staying with Scrum if it fits the work and not switching methods for prestige. Swapping to Kanban because a director wants something that "sounds advanced" is replacing a working copier because the catalog called another one advanced. Fit beats prestige on civic delivery teams.
Switching to Kanban to match the director's prestige goal fails because branding is not a flow reason. Running Scrum and Kanban in parallel for one PI as a bake-off fails because dual-method focus splits attention and confuses working agreements. Asking the SPC to recertify the team only after they adopt Kanban fails because gating "advanced" status on Kanban treats hierarchy as improvement.
Exam caveat: Team Kanban is valuable in the right context; it is not a maturity badge above Scrum. Operational check: document why Scrum currently fits vital-records work, educate the director with flow outcomes rather than certificate optics, decline prestige-driven switches, and reopen method choice only when arrival or planning evidence shows misfit. Vital-records teams that already deliver predictably in Scrum should protect that fit until evidence—not certificates—shows a different method would serve residents better.