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. Mid-Sprint on a school-enrollment product, when the Product Owner starts rewriting Developer tasks and assigning who will build each validation rule, the Product Owner should instead leave the Sprint Backlog plan to the Developers and collaborate on Product Backlog order and clarification of the what. Accountability for value does not include directing individual work.
Continuing to assign tasks because the Product Owner is accountable for value confuses product ordering with task dispatch. Asking the principal to approve each task before Developers may change the plan adds an external approval hierarchy. Converting the Daily Scrum into a task-assignment meeting the Product Owner chairs corrupts Daily Scrum into status command.
Exam caveat: PSPO II separates Product Backlog (PO) from Sprint Backlog plan (Developers); mid-Sprint task rewriting is an anti-pattern.
Operational check: stop editing Sprint Backlog tasks, clarify enrollment outcomes on Product Backlog items, and let Developers adapt their own plan toward the Sprint Goal.