The student-information team's Iteration Planning ignores Team PI Objectives and starts a disconnected local list. What should the Scrum Master / Team Coach reconnect?
Select an answer to reveal the explanation.
Short Explanation
Planning a student-information sprint like a private to-do pad ignores the PI map the ART already drew. Team events exist to move Team PI Objectives, not a side list. Point the plan back at those objectives or the iteration is sightseeing.
Full Explanation
Team PI Objectives are the contract between the Agile Team and the ART for the Planning Interval. Iteration Planning, review, and related events should pull work that advances those objectives. Ranking by overtime, substituting a director steering list, or waiting until I&A disconnects team cadence from ART outcomes. The Scrum Master / Team Coach reconnects the student-information events to the PI objectives so local plans stay true.