Product Owner

Esta página es una versión traducida de la página Propietario del producto. La traducción está completa al 100 %.

⏱ 5 min · 📅 2026

The Product Owner is one of the roles of technical Scrum. This is the person who makes decisions on behalf of the customer and is responsible for the value of the product: they decide what goes into the Product Backlog, in what order, and which criteria define its success.

Description

To simplify communication and decision-making, this role must fall to a single person. If the customer is a large organization or one with several departments, it may adopt whatever form of internal communication it deems appropriate, but only one person joins the development team on behalf of the customer, and this person must have sufficient knowledge of the product and the necessary authority to make the decisions that fall to them.

For in-house development within the company itself, this role is usually taken on by the product manager or the head of marketing. For development for external clients, it falls to the person responsible for the client's procurement process.

Depending on the circumstances of the project, they may even delegate to the development team or to someone they trust, but the responsibility always remains theirs.

Responsibilities

The Product Owner is the one who:

Has the final say on what the end result will look like and on the order in which the successive increments are built: what goes into and what comes out of the Product Backlog, and the priority of the features.
Knows the product plan, its possibilities, and its investment plan, as well as the expected return on the investment made, and is accountable for the dates and features of its different versions.

Skills

To perform this role, it is necessary to:

Know the customer's business environment thoroughly, along with their needs and the goal pursued with the system being built.
Have the product vision, as well as the specific needs of the project, in order to prioritize the work efficiently.
Have sufficient authority and knowledge of the product plan to make the necessary decisions during the project.
Be able to communicate clearly and directly with both the technical team and the business stakeholders.

The Product Owner in AI-Enabled Teams

As the cost of building decreases, the primary bottleneck shifts toward deciding what is actually worth building—a domain that falls squarely under the purview of the Product Owner. Their role becomes increasingly significant with the advent of AI, provided it evolves from a tactical focus to a strategic one; those who merely write and prioritize backlog items are performing the very tasks that AI is best equipped to assist with.

Maintains the vision and defines how the work being built will be validated.
Treats every backlog item as a hypothesis: what problem it solves, for whom, and how it will be determined whether that problem has been successfully addressed.
Decides where AI adds value versus where it merely generates volume. While AI can assist in drafting, grouping, or identifying duplicates within the backlog, the decisions regarding what gets included—and in what order—remain the Product Owner’s responsibility.

Some guides refer to this role as "product architect"; this is not a term used in the standard framework.

Common mistake

Having a Product Owner without real authority. A Product Owner who needs to check every decision with other people before committing destroys the team's workflow: Sprint Planning becomes tentative, conversations about priority fail to produce agreements, and the team ends up working with scope uncertainty. If the person assigned to this role lacks the authority to make product decisions, that organizational structure must be resolved before adopting Scrum.