product owner
/ˈprɒd.ʌkt ˈəʊ.nə(r)/noun
In Scrum, the product owner is accountable for maximizing product value and managing the product backlog. They order the work and communicate the product goal.
The product owner discussed new customer requests with the team and put the most important improvement at the top of the backlog.
The product owner connects user and stakeholder needs with the Scrum team's work. The role requires decisions: which problem comes first, which functionality can wait and which outcome is valuable? Those decisions appear in the product goal and Glossary · In briefbacklogA backlog is an ordered, evolving list of work for a product or project. Its order helps a team decide what to investigate or implement first.Read more.
What is a product owner responsible for?
In Scrum, the product owner is accountable for maximizing product value. This includes effective backlog management: defining the product goal, making backlog items clear, ordering the work and ensuring the backlog is understandable and visible.
The product owner can delegate backlog tasks but remains accountable for the result. In Scrum, the product owner is one person, not a steering committee. Stakeholders can put forward needs and interests; the product owner weighs that information and decides on the order.
Working with developers and stakeholders
A product owner mainly determines what the product should achieve and why particular work matters. Developers determine how to implement it technically. During Glossary · In briefrefinementRefinement is the ongoing clarification, breakdown and estimation of backlog work so the team understands what each item involves.Read more, they discuss intent, dependencies and Glossary · In briefacceptance criteriaAcceptance criteria are agreed, testable conditions that a product, feature or change must meet to be accepted.Read more together so a backlog item is clear enough to plan.
After a Glossary · In briefsprintA sprint is a short, fixed period in which a team develops an agreed part of the software. Afterwards, you review the result and decide on the next priorities.Read more, the product owner, team and stakeholders review what was delivered and what they learned. The backlog can change accordingly. Its order stays aligned with user needs, technical feasibility and progress towards the product goal.