Ir al contenido

Product Vision

De Scrum Manager BoK
Esta página es una versión traducida de la página Visión del producto. La traducción está completa al 100 %.
⏱ 3 min  ·  📅 2026
The product vision is a statement that describes the product's reason for being, its long-term purpose, and the value it aims to deliver to users and the business. For the Product Owner, it is the strategic compass that guides prioritization and planning decisions, and the point of reference that aligns the team around a common goal.

The vision is not a list of features: it is a picture of the change the product aims to bring about in its users' lives or in the market. It should be possible to communicate it in a few sentences, and anyone involved in the project should be able to understand it.

Purpose

The product vision serves three main functions:

  • Alignment: it ensures that everyone involved—team, Product Owner, stakeholders—shares the same understanding of the ultimate goal, preventing each person from working toward a different interpretation.
  • Decision criterion: when the Product Owner must prioritize between two features or decide what goes into the product and what stays out, the vision provides the reference criterion.
  • Motivation: a well-formulated vision connects daily technical work with a meaningful purpose, which has an impact on the team's commitment.

Characteristics of a good vision

An effective product vision should:

  • Define the problem or need that the product will solve.
  • Identify the target audience it is aimed at.
  • Describe the main value it will deliver.
  • Inspire and motivate the team and the stakeholders.
  • Guide long-term planning as a basis for prioritizing features and defining success criteria.

How to Formulate It

A common technique for formulating the vision is the elevator pitch format, which requires summarizing in a few sentences who the user is, what problem they have, how the product solves it, and what sets it apart from existing alternatives.

Another tool that helps make the vision specific from the start of the project is the Agile inception deck, especially its "Why are we here?" activity and the product box activity.

Common mistake

Confusing the vision with the backlog or the roadmap. The vision describes the destination; the Product Backlog and the roadmap describe the path. A vision that lists specific features or planned releases is no longer a vision; it has become a plan. When the plan changes—and in agile projects it changes often—the vision should remain valid.

Resources

📄 Product Owner v.2.0Free download (in Spanish) · Scrum Manager

🏦 Skill Agile InceptionState of the art and development guide · Skill Arena

See also

Do you 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.