A public-health director wants to skip the Inspect and Adapt problem-solving workshop because the ART already knows testers are the issue. What should the Scrum Master / Team Coach protect?
Select an answer to reveal the explanation.
Short Explanation
"We already know it's the testers" is a scapegoat with a name tag, not a diagnosis. Public-health flow problems live in the system. Protect the structured workshop instead of skipping it.
Full Explanation
I&A problem-solving inspects the system; it must not start from a pre-baked scapegoat. A public-health director who wants to skip the workshop because “testers are the issue” asks the coach to rubber-stamp blame. The Scrum Master / Team Coach protects a structured retrospective and root-cause workshop so lab and delivery systems can improve without ritual sacrifice. Scapegoats block learning and harm people.
A memo naming lab testers as the defect so the workshop can be cancelled institutionalizes blame. A closed-door session with the director only excludes those who know the work. Immediate performance plans for testers in place of root-cause analysis punish a role instead of fixing flow.
Exam caveat: problem-solving is evidence-based and systemic, not a confirmation meeting for a villain. Operational check: open public-health I&A problem-solving with data from demo and measures, not with a named scapegoat.
Municipal ARTs feel Inspect and Adapt choices as safer shelter intake, fairer elections, cleaner water data, and clearer permits for the public. Keep facilitation transparent, include the whole Agile Team, and verify improvement items enter real backlogs with owners and check dates. After the event, confirm the next iteration planning agenda references the agreed experiments so civic delivery actually changes.