Parking-enforcement product teams let a model generate and run the entire iteration-planning agenda unattended. What should the Team Coach reject?
Select an answer to reveal the explanation.
Short Explanation
A draft agenda is a grocery list; running planning unattended is leaving the cart in the aisle. AI can sketch the parking-team agenda. A human still has to facilitate the conversation, because planning is judgment, not a playlist.
Full Explanation
Parking-enforcement product teams may use AI to draft an iteration-planning agenda, but the Team Coach must reject over-automation of facilitation: a human still facilitates with judgment. A draft agenda is a grocery list; running planning unattended is leaving the cart in the aisle. Reading the room, protecting outcomes, and adapting the conversation remain Scrum Master / Team Coach responsibilities on civic product teams.
Rejecting any AI draft even when a human still facilitates fails because responsible draft support is allowed and can cut administrative setup time without replacing judgment. Rejecting human facilitation because an unattended model is supposedly required SAFe practice fails because unattended model-run planning is not a Framework requirement. Substituting the model's timeboxes as committed PI scope and dropping team participation fails because generated schedules are not team commitments.
Exam caveat: the advanced stance is draft-then-facilitate, not replace-the-facilitator and not ban-all-drafts. Operational check: allow AI agenda drafts for parking-team planning, keep a human facilitator in the session, ensure the team shapes the plan and goals live, and never promote unattended model output into PI commitments.