Product Owner
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.
Role evolution in AI-enabled teams: the Product Architect
In teams working with generative AI tools, the Product Owner role evolves toward what Scrum Manager's guide Scrum en equipos con IA [Scrum in Teams with AI, in Spanish] calls the Product Architect:
- The backlog stops being a list of features and becomes a set of hypotheses to validate. AI can build fast; the Product Architect decides what is worth building.
- Manages the productivity paradox: the team produces more thanks to AI, but that only generates value if there is strategic validation behind it. The strategic question is no longer "can we build it?" but "should we build it, and why?"
- Works in close coordination with the product builders to define specs (not just user stories) when the work will be carried out by AI.
- Needs data literacy skills and the ability to design validation experiments, in addition to classic product skills.
- Decides when an idea moves from the fast lane (vibe coding, rapid prototyping) to the robust lane (vibe engineering, quality production).
The key indicator for the Product Architect is not how many items the team delivers, but how many of those items solve real user problems. AI productivity amplifies strategic successes and strategic mistakes alike.
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.
Resources
📄 Product Owner v.2.0 [in Spanish]Free download · Scrum Manager
📄 Scrum Master v.4.0 [in Spanish]Free download · Scrum Manager
📄 Scrum Master en equipos con IA [Scrum Master in Teams with AI, in Spanish]Free download · Scrum Manager
See also
Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.