The special-assessment portal team cannot choose a validation message or split a story without a monthly steering committee. What should the SM/TC coach?
Select an answer to reveal the explanation.
Short Explanation
Waiting a month to pick a validation sentence is a stop sign in the team's own driveway. High-performing teams decide the small stuff in their scope. Leave the steering committee for true economic trade-offs, not copy tweaks.
Full Explanation
Decentralized decision-making removes wait queues for choices inside the team’s scope. When the special-assessment portal team cannot choose a validation message or split a story without a monthly steering committee, trivial decisions become civic delivery delays. The Scrum Master/Team Coach should coach pushing those decisions to the team (with clear guardrails) so steering focuses on true strategic items.
Routing every UI copy change through the committee fails by concept: it maximizes delay for consistency theater. Pausing delivery until the committee writes a decision tree for all stories fails by concept by stopping value while waiting for exhaustive bureaucracy. Escalating every split to program leadership fails by concept because it trains learned helplessness and floods leadership with micro-decisions.
Exam caveat: SAFe principle of decentralizing decision-making distinguishes frequent/time-critical/local decisions (team) from infrequent/long-lasting/global ones (elevated). Validation copy and story splits usually belong with the team serving special-assessment applicants.
Operational check: agree a decision matrix with steering for what the portal team may decide alone, apply it for two iterations, measure wait time formerly spent on committee queues, and escalate only decisions that truly need committee scope.