A city parks app team using Scrum debates who decides the order of backlog items for the next sprint of trail-map features. How does Scrum typically assign that prioritization responsibility compared with some Kanban service-management setups?
Select an answer to reveal the explanation.
Short Explanation
Think of the Product Owner like the parks department’s feature curator— they rank what citizens get next. Scrum puts backlog order squarely with the PO, while some Kanban setups hand service managers different ordering duties. Same ‘who decides next’ question, different role boxes.
Full Explanation
On a city parks app team using Scrum, backlog prioritization for the next sprint of trail-map features is typically owned by the Product Owner, whereas some Kanban service-management setups may place ordering with different service roles. That contrast helps associates see that "who ranks the work" is method-dependent: Scrum assigns Product Backlog order to the Product Owner accountability, while Kanban variants can locate ordering differently in service management designs.
Claiming the Development Team votes weekly and the Scrum Master breaks ties using velocity charts alone fails conceptually because Scrum does not assign backlog ordering to team votes with Scrum Master tie-breaks via velocity. Claiming the city CIO must approve every backlog rank change before any story can move fails because that centralizes ranking outside the Product Owner model Scrum describes. Claiming Kanban and Scrum both forbid a single person from ordering work so ranking is always random fails because both can have clear ordering authority; neither mandates randomness.
Exam caveat: At CAPM depth, remember Product Owner owns Product Backlog priority in Scrum; do not invent CIO-approval or random-ranking rules as core method components. Operational check: ensure the parks Product Owner visibly orders trail-map items, communicate priority to the Developers, and if comparing to a Kanban service desk, document which service role owns intake order there.