Leadership wants to replace the whole recycling-route team based on one bad PI. How should the Scrum Master / Team Coach respond?
Select an answer to reveal the explanation.
Short Explanation
One bad PI is a weather report, not a verdict. Recycling-route teams live in storms of impediments. Look at the trend and the context before anyone talks about replacing the whole roster.
Full Explanation
Leadership wanting to replace a whole recycling-route team based on one bad PI should be met with trend analysis across PIs plus impediment context before judging the team. Single-PI noise—storms, vendor outages, policy shocks, or unusual tonnage—can wreck one period without proving the team is incapable of municipal service. Supporting full-team replacement after any missed PI is brittle and destroys tacit knowledge about routes and residents. Asking the Release Train Engineer to reconstitute the team during the next IP iteration escalates to train restructuring without diagnosis. Ranking the PI as a failed earned-value period and closing the team immediately imports predictive shutdown logic foreign to SASM team coaching. Exam caveat: SASM assesses teams with multi-PI trends and systemic impediments; one-PI replacement and earned-value shutdowns are wrong. Operational check: chart outcomes and flow across several PIs for the recycling-route team, list major impediments outside team control, coach targeted improvements, and only then discuss structural changes with leadership if the trend remains poor after impediments are addressed. Document the context so a single bad winter PI cannot alone justify dissolving the civic team.