Last PI's Inspect and Adapt improvement stories for the building-permits ART never entered PI Planning. How should the Scrum Master / Team Coach treat those items?
Select an answer to reveal the explanation.
Short Explanation
Improvement stories that never hit PI Planning are New Year's resolutions in a drawer. For the permits ART they are real backlog work. Plan them next PI or Inspect and Adapt was theater.
Full Explanation
Improvement backlog items from I&A are real work that must be considered in the next PI Planning. Building-permits improvements left in a lessons-learned archive never change permit flow for applicants. The Scrum Master / Team Coach treats those items as candidates alongside Features so improvement competes transparently for capacity.
Archiving improvements as lessons-learned so PI Planning stays feature-only buries change. Handing the list to HR as staffing and dropping it from the ART backlog misroutes process work. Waiting until the next fiscal year so improvement never competes with Features delays learning indefinitely.
Exam caveat: close the loop from I&A into PI Planning. Operational check: carry permits improvement stories into PI Planning and make accept/defer decisions visible.
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.