Sprint Planning is starting for the transit trip-planner. What is the Product Owner’s job in that event?
Select an answer to reveal the explanation.
Short Explanation
Sprint Planning is not the Product Owner handing out trip-planner chores like a dispatcher. Bring a clear Product Goal and an ordered backlog people can actually discuss, then craft the Sprint Goal with the team. Developers still forecast what fits.
Full Explanation
In Sprint Planning the Product Owner ensures attendees understand the Product Goal and the most important ordered Product Backlog items, then collaborates so the Scrum Team crafts a Sprint Goal and Developers forecast the work. For a transit trip-planner, that preparation and collaboration—not dispatching chores—is the Product Owner's job in the event and the start of empiricism for the Sprint.
Writing the Sprint Goal alone before the event and assigning technical tasks to named Developers steals team ownership of the goal and of how. Skipping Planning and sending a ranked spreadsheet because ordering replaces collaboration withholds the conversation the timebox is for. Turning Planning into a stakeholder status briefing and postponing Sprint Backlog selection converts a planning event into theater without a forecast.
Exam caveat: PSPO II Sprint Planning items expect PO preparation of Product Goal and ordered backlog plus collaborative Sprint Goal formation—not solo mandates or status briefings.
Operational check: before Planning, refine the top trip-planner items against the Product Goal; during Planning, co-create a Sprint Goal and accept the Developers' forecast without assigning named tasks.