Elections-systems team events always run over because there is no timebox or parking lot. How should the Scrum Master / Team Coach protect outcome focus?
Select an answer to reveal the explanation.
Short Explanation
An elections meeting with no clock is a precinct that never closes. Timeboxes and a parking lot are not rudeness; they keep the session pointed at the outcome. Park the side trails so the team still leaves with a plan, an inspected increment, or an experiment.
Full Explanation
Timeboxes and parking lots protect outcome focus. Elections-systems events that always run over lose the planned result—ready stories, a reviewed increment, or an experiment. The Scrum Master / Team Coach enforces the timebox, parks off-topic items, and returns to purpose so election integrity work stays disciplined under pressure. Importance is not an excuse to abandon structure.
Letting discussions run until everyone has spoken sacrifices the outcome to airtime. Canceling timeboxes because election work is “too important to stop” creates unbounded meetings and weaker results. Handing leftover agenda to the RTE after hours dumps unfinished facilitation upward.
Exam caveat: facilitation skill includes ending on time with the outcome achieved or explicitly deferred. Operational check: start elections events by stating outcome and end time; park digressions visibly.
In municipal ARTs, residents experience these coaching choices as faster or slower public services—licensing lines, housing decisions, water bills, snow routes, and emergency response—so keep events and buffers tied to inspect-and-adapt outcomes. Record the decision, the owner, and the next inspection date so the team can verify civic impact.