← Agile and Scrum: Flexible Project Management
Lesson
Lesson 3.1 — Product Owner: accountable for value
Describe what the Product Owner is accountable for and how they manage the Product Backlog.
Who Is the Product Owner?
The Product Owner: One Person, One Backlog
The Product Owner (PO) is the single person accountable for maximizing the value of the product resulting from the work of the Scrum Team. This is not a committee or a shared role — one person owns these decisions. If someone else in the organization wants to change the order of the Product Backlog, they must go through the Product Owner.
The PO owns and orders the Product Backlog. 'Orders' means prioritizes: the PO decides which items appear at the top and will be worked on soonest. The PO also communicates the Product Goal — the long-term objective that gives direction to the entire team — and ensures that the backlog is transparent, visible, and understood by everyone who needs to see it.
Important boundaries: the Developers decide HOW to build the product (they choose the techniques, tools, and approach). Stakeholders — managers, customers, users — can provide input and feedback, but they do not own or order the backlog. Only the Product Owner does. This clear ownership prevents conflicting priorities and keeps the team focused on what delivers the most value.
Lesson notes
The Product Owner: One Person, One Backlog
The Product Owner (PO) is the single person accountable for maximizing the value of the product resulting from the work of the Scrum Team. This is not a committee or a shared role — one person owns these decisions. If someone else in the organization wants to change the order of the Product Backlog, they must go through the Product Owner.
The PO owns and orders the Product Backlog. 'Orders' means prioritizes: the PO decides which items appear at the top and will be worked on soonest. The PO also communicates the Product Goal — the long-term objective that gives direction to the entire team — and ensures that the backlog is transparent, visible, and understood by everyone who needs to see it.
Important boundaries: the Developers decide HOW to build the product (they choose the techniques, tools, and approach). Stakeholders — managers, customers, users — can provide input and feedback, but they do not own or order the backlog. Only the Product Owner does. This clear ownership prevents conflicting priorities and keeps the team focused on what delivers the most value.