Ir al contenido

Product operating model

De Scrum Manager BoK
Esta página es una versión traducida de la página Modelo operativo de producto. La traducción está completa al 100 %.
The product operating model is the set of decisions regarding structure, funding, governance, metrics, and culture through which an organization builds and operates products on an ongoing basis. The organization is structured around enduring products and the stable teams that manage them, moving away from an organization based on temporary projects or siloed functions. It is framed as a set of principles that each organization applies in its own way, rather than as a prescribed methodology or process.

From project to product

Most organizations arrive at the product model from one of three starting points: technology in service of the business, the project-based approach, or "feature teams." All three share the assumption that work eventually comes to an end—an assumption the product model challenges, as a product is nurtured and evolved for as long as it continues to deliver value.

The shift to a product-centric model entails three simultaneous changes: the organizational unit shifts from a temporary project to a persistent product; the focus of responsibility moves from adhering to a plan to achieving outcomes; and the relationship with time transitions from a schedule with a defined end to a continuous cadence of delivery and learning. Mik Kersten coined the term for this shift in *Project to Product* (2018) and revisited it in *Output to Outcome* (2026), arguing that as AI accelerates the building process, the bottleneck shifts to the operating model itself.

Five Interdependent Dimensions

Scrum Manager groups the model’s decisions into five dimensions. This synthesis provides a way to navigate the model—distinct from Cagan’s three dimensions or the four key areas of APOM.

Dimension Project-based Model Product-based Model
Structure Teams assembled for each project and dissolved upon completion Long-standing, cross-functional teams organized around products and value streams
Funding Project-based budgeting, defined by scope and timeline Ongoing funding for products and teams, adjusted based on evidence of results
Governance Approval via phases and committees Authority delegated to teams within clear constraints; lightweight governance focused on verifying outcomes
Metrics Deliverables and adherence to the plan Outcomes and evidence of value
Culture Deadlines and certainty Learning, transparency, and psychological safety

The key factor is coherence across all five dimensions. For instance, demanding empowered teams while maintaining project-based funding creates friction and often leads to the failure of the transition. For this reason, the model is the responsibility of leadership; no single department can change it on its own.

Two Reference Frameworks

  • Product Operating Model (Marty Cagan and SVPG), articulated primarily in *Transformed* (2024). It consists of three dimensions—how things are built, how problems are solved, and how decisions are made regarding which problems to solve—along with twenty principles grouped into five concepts: culture, strategy, teams, discovery, and delivery. Cagan deliberately avoids the adjective "agile" and is wary of an over-reliance on process.
  • Agile Product Operating Model (APOM, Scrum.org), rooted in Scrum, Nexus, and evidence-based management. As of 2025, it was defined by seven characteristics; since January 2026, it has been framed through guiding principles across four key areas (strategy, people, structure, and value cycle) and four core principles (evidence-based, empirical agility, end-to-end ownership, and outcome-oriented), with each principle linked to an evidence-based metric.

Both frameworks share the same core tenets: product over project, outcomes over outputs, empowered teams, evidence-based governance, and continuous delivery. They differ in their foundational grounding, the emphasis placed on process, and their terminology. Mik Kersten offers a third perspective, centered on value streams, which he presents as a continuation of his 2018 work.

What is a product

The guiding principles of the APOM define a product as a vehicle for delivering value, with clear boundaries, known stakeholders, and well-defined users or customers. The extent to which something qualifies as a product is a matter of degree; when something does not fit perfectly, the model is applied with some nuance. Drawing boundaries incorrectly creates dependencies and overlaps between teams, because defining products is, in practice, a decision regarding organizational design (see Conway's Law).

Operating model and scaling frameworks

The operating model defines the "what" and the "why"; a scaling framework—such as SAFe, LeSS, or Nexus—is one possible approach to the "how," serving as a layer of instantiation. Adopting a framework does not transform an organization into a product-oriented organization if it continues to fund by project, measure deliverables, and make decisions through committees (see Agile scaling models).

The transition

The transition is holistic and incremental. It is holistic because, wherever progress is made, all five dimensions advance together; it is incremental because progress occurs product by product, at varying paces, along a continuous journey. Managing it as a project—with a defined scope, a plan, and an end date—would merely replicate the very model one seeks to move away from. Sponsorship from senior management is a necessary condition, as only they can mobilize the necessary funding, governance, and incentives (see Management involvement).

Common Pitfalls

  • Looking for a "recipe." Treating the model as a rigid framework with numbered steps, rather than as a set of principles that each organization must adapt to its own context.
  • Renaming things and declaring victory. Simply relabeling existing work as "product" without changing funding, governance, or incentives.
  • Changing only one dimension. Demanding empowered teams while maintaining project-based funding, activity-based metrics, or phase-gate governance.
  • Accelerating the project-based model with AI. Speeding up production within the same model only multiplies deliverables without bringing you any closer to actual outcomes.

Resources

🏦 Agile product operating modelSkill Arena · Scrum Manager

References

See also

Want to advance your Agile journey? You can look for upcoming courses and exams, or progress 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 where you can practice and assess your Agile skills at your own speed.