A new coach on the DMV-licensing team cancels iteration retrospectives, saying Inspect and Adapt now covers all improvement. What should continue?
Select an answer to reveal the explanation.
Short Explanation
Inspect and Adapt is the PI's big tune-up, not a reason to skip oil changes. The DMV team still needs iteration retrospectives. Keep both: team-level during the PI, ART-level at the end.
Full Explanation
Team retrospectives during the PI and ART-level Inspect and Adapt at PI end both continue. A new DMV-licensing coach who cancels iteration retros because I&A “covers all improvement” removes the fast local loop. Licensing flow problems should not wait an entire PI. The Scrum Master / Team Coach keeps both cadences.
Canceling team retrospectives permanently misunderstands scope differences between team and ART improvement. Merging every team retro into a monthly all-hands with no ART problem-solving blurs both events. Replacing both with a year-end suggestion box abandons cadence entirely.
Exam caveat: I&A does not replace iteration retrospectives. Operational check: restore DMV team retros each iteration and keep PI I&A for cross-team systemic issues.
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. Re-check service metrics at the agreed date.