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
In Scrum, the Product Owner is accountable for maximizing product value and for ordering the Product Backlog. That component is explicit. Kanban implementations focused on IT service management may assign work selection or class-of-service decisions to service managers or similar roles rather than a Scrum Product Owner. CAPM candidates should distinguish those framework components instead of assuming identical role titles across all adaptive methods.