On the 911 CAD/RMS integration ART, nobody can say who prioritizes the Program Backlog. Who holds that content authority?
Select an answer to reveal the explanation.
Short Explanation
The Program Backlog is the ART's what-next list for 911 CAD/RMS. Product Management owns that list. The RTE keeps the event running; the architect guides the how—not the priority of every feature.
Full Explanation
Product Management owns ART-level content authority and Program Backlog prioritization. On a 911 CAD/RMS integration ART, if nobody can say who prioritizes the Program Backlog, the RTE should clarify that Product Management holds that authority—not the RTE, a dispatch supervisor acting as Scrum Master for all teams, or the System Architect sequencing by technical interest. Facilitation is not ranking every feature. A 911 dispatch supervisor Scrum Master does not inherit Program Backlog authority by proximity to operations. Architects guide technical feasibility and runway; they do not replace Product Management's prioritization of CAD/RMS value. Exam caveat: Product Management prioritizes with input from architects, Business Owners, and teams; ownership of the decision still sits with Product Management. Operational check: Name the Product Management role on the 911 ART, review the top Program Backlog items with them before ART Sync, and stop treating the RTE as the default prioritizer. In municipal settings, pressure to look busy, compliant, or politically safe is constant; the RTE earns trust by holding the principle through that pressure and verifying the next cadence event shows improved civic delivery, not just a quieter meeting. Capture the before/after signal so sponsors see the operational evidence.