Mid-Sprint on a school-enrollment product, the Product Owner starts rewriting Developer tasks on the Sprint Backlog and assigning who will build each validation rule. What should the Product Owner do instead?
Select an answer to reveal the explanation.
Short Explanation
The Sprint Backlog is the Developers' game plan, not the Product Owner's chore chart. Value comes from ordering the what on the enrollment product, not from handing out tasks. Grabbing the marker mid-Sprint just turns the team back into a work queue.
Full Explanation
Developers own the Sprint Backlog as their plan for achieving the Sprint Goal; they decide how to turn selected Product Backlog items into a Done Increment. The Product Owner remains accountable for Product Backlog order and for clarifying desired outcomes, but assigning tasks undermines self-management. Accountability for value does not include directing individual work. A principal-approved task list or a Product Owner-chaired Daily Scrum is a status hierarchy, not Scrum.