During PI Planning for an open-data and civic-engagement ART, System Architects start a three-hour monologue on every platform decision before draft-plan breakouts begin. How should the RTE facilitate?
Select an answer to reveal the explanation.
Short Explanation
Architecture briefing is a weather report, not a three-hour lecture. Give the civic-engagement teams enough sky to plan, then get them into breakouts. Extra detail belongs in office hours, not the whole room.
Full Explanation
Architecture guidance belongs in PI Planning, but it must be timeboxed so draft-plan breakouts still happen. When System Architects on an open-data and civic-engagement ART start a three-hour monologue on every platform decision before breakouts, the RTE should timebox the briefing to the agenda slot and park remaining detail for office hours or breakouts. Letting the briefing run until every open-data API is fully specified turns planning into design theater and starves team planning capacity. Moving architecture guidance entirely out of PI Planning into a closed architect-only workshop after the event removes runway input when teams need it. Replacing architects with a recorded webinar overnight before Day 2 severs dialogue and questions. Citizens consuming open data and civic-engagement services need teams that leave planning with actionable plans, not a catalog of unresolved platform lectures. Exam caveat: complex civic platforms may need deeper sessions, but those deepen during breakouts or follow-ups—they do not erase the ART planning agenda. Operational check: enforce the architecture timebox with a visible timer, capture parking-lot questions, and start team breakouts on schedule. Publish the parked architecture questions with owners so the civic engagement backlog still moves after the event.