Two weeks before PI Planning, the parks reservation and facility ART backlog is stale. What should the RTE do?
Select an answer to reveal the explanation.
Short Explanation
A stale parks backlog is a readiness problem, not a cue for the RTE to become Product Owner. Coach the people who own content to explore and refine before PI Planning. Writing the stories yourself, or waiting until the two-day event to invent them, both miss the job.
Full Explanation
Backlog readiness before PI Planning is a Product Management, Product Owner, and team responsibility supported by continuous exploration and refinement. When a parks reservation and facility ART backlog is stale two weeks out, the RTE should coach those roles to restore refinement—not become the Product Owner. The facilitation duty is to make the readiness gap visible early and help the content owners recover a plannable backlog for civic reservation services. Rewriting every reservation story personally so the backlog looks ready on planning day creates false readiness, hides the real capability gap, and sets the RTE up as the permanent author. Canceling PI Planning until the RTE has approved each parks feature in a change-control board invents a gate that SAFe does not place on the RTE and delays learning. Instructing Scrum Masters to freeze refinement and wait for the planning weekend to invent the work guarantees low-quality plans and exhausted breakouts. Exam caveat: The RTE can facilitate backlog refinement workshops and readiness checklists; coaching the process is different from owning story content. Operational check: Run a readiness review covering features, enablers, capacities, and Business Owner prep; track open refinement actions to named Product Owners before parks PI Planning starts.