Shelter-intake staff are told the Innovation and Planning iteration is "for developers only." What should the Scrum Master / Team Coach include?
Select an answer to reveal the explanation.
Short Explanation
IP that only invites developers is a shelter drill that leaves the intake desk at the curb. Innovation, learning, I&A, and planning prep belong to the whole Agile Team. Bring the specialists, not just the coders.
Full Explanation
IP purposes include the whole Agile Team—innovation, learning, Inspect and Adapt, and planning prep—not developers only. Shelter-intake specialists hold operational knowledge essential to those activities. The Scrum Master / Team Coach includes business and operations members so IP improves the full value stream for people seeking shelter. Excusing them so developers “code in quiet” recreates silos inside the buffer.
Excusing business and operations members from IP so developers can code quietly excludes critical voices. Running a developer-only hackathon and skipping I&A and planning prep for the rest of the team abandons IP breadth. Sending specialists back to the queue while developers use IP steals capacity from shared improvement.
Exam caveat: Agile Team means all roles on the team participate in IP purposes. Operational check: invite shelter-intake specialists to IP planning and I&A prep, not only to delivery standups.
Municipal ARTs feel Inspect and Adapt and IP 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.