Product Management asks the parks-reservation Team Coach to write every Team PI Objective so “planning goes faster.” How should the coach respond?
Select an answer to reveal the explanation.
Short Explanation
Faster planning that skips the parks team is just the coach doing the team's homework. Team PI Objectives are the team's commitments, not a Word doc the Scrum Master ghostwrites. Facilitate the conversation; do not become the author.
Full Explanation
Team PI Objectives for a parks-reservation team are created by the Agile Team during PI Planning; the Scrum Master / Team Coach facilitates that conversation and refuses to author the objectives unilaterally. Speed that skips the people who will deliver reservation value is not SAFe acceleration—it is ghostwriting commitments the team never owned. Facilitation without overreach is the advanced stance Product Management should hear.
Drafting all Team PI Objectives overnight so Product Management can skip the team conversation fails because unilateral authorship removes team ownership of what parks work will be delivered. Copying last PI's objectives and raising uncommitted stretch to absorb risk fails because recycled objectives and inflated stretch hide real capacity and risk instead of planning honestly. Handing objective authorship to the Release Train Engineer fails because the RTE facilitates the train, not the team's ownership of its own objectives.
Exam caveat: Product Management can clarify ART priorities and constraints, but that input does not authorize the coach to write Team PI Objectives alone. Operational check: schedule facilitated objective conversations with the parks team during PI Planning, capture objectives the team articulates, reject overnight ghostwriting requests, and confirm at confidence vote that the team recognizes the objectives as its own.