Agile teams move fast enough that a vague answer to "what should we build next" costs a sprint, not a memo. Scrum's response was to make one person accountable for that answer at all times. The product owner exists so the team never has to guess what matters most.
In this glossary topic:
What is an agile product owner?
An agile product owner is the member of a Scrum team accountable for maximizing the value of the team's work. The role owns the product backlog: what goes on it, how it is ordered, and what "done" means for each item. Where the rest of the team owns how work gets built, the product owner owns what gets built next and why.
What does a product owner do?
The visible work is backlog management: writing and refining items, ordering them by value, and keeping the top of the list ready for sprint planning. The invisible work is the harder half: absorbing input from stakeholders, users, and data, then converting it into one prioritized sequence the team can trust. The product owner also accepts or rejects finished work against its criteria, and answers the team's questions daily, because an unavailable product owner converts directly into blocked developers and guessed requirements.
How does a product owner differ from a product manager?
Product owner is a role inside a delivery framework; product manager is a job spanning the whole product. The product manager looks outward and forward, at markets, strategy, and discovery, while the product owner looks at the team and the next sprint. In many companies one person carries both, and the title in use says more about the org chart than the work. The distinction earns attention at scale, where a product manager may set direction across several teams, each with its own product owner translating that direction into a backlog.
