Developers on the parks irrigation-scheduling product ask the Product Owner to write every technical task for the Sprint. What should the Product Owner clarify?
Select an answer to reveal the explanation.
Short Explanation
The Product Owner picks which field gets water and why; the crew still decides how to lay the pipe. Writing every technical task turns the PO into a back-seat engineer and steals the Developers’ “how.” Keep order and purpose; leave the Sprint’s craft with the people doing the work.
Full Explanation
Within a Sprint, Developers are accountable for creating a plan and for how the Sprint Goal is achieved. The Product Owner remains accountable for the Product Backlog—what, why, and order—not for tasking irrigation-controller implementation. When the Product Owner or an outside architect specifies every technical task, self-management collapses. Clarifying that boundary keeps both accountabilities intact.