Informative

Agile Product Operating Model: New Version of the Skill in Skill Arena

Automatic translation · View original

Topic illustration: Agile Product Operating Model: New Version of the Skill in Skill Arena

The cheaper it becomes to build, the more the way an organization decides, funds, and measures what it builds matters. We are publishing the November 2026 version of the skill "Agile Product Operating Model", with a renewed State of the art and guide: it describes the Scrum.org model as it has been formulated since 2026, incorporates what artificial intelligence changes in the product model and what it leaves the same, and links the Scrum Manager BoK pages that cover each concept.

Why a New Version

In June 2026 we published the first version of this skill, devoted to running an organization by product instead of managing work as a succession of projects. That scope still holds. When we reviewed it against current sources, however, we found one factual error and quite a bit to update.

The error was in one of the two reference formulations. In January 2026 Scrum.org published the guiding principles of its Agile Product Operating Model (APOM) and stopped describing it with the seven characteristics we had recorded. Its survey on the model, published that same month with responses from more than 130 organizations, also shows silos and structural impediments that limit the real autonomy of teams.

What needed updating comes mainly from AI. Between July and November 2026, Marty Cagan published several articles on SVPG about its effect on the product model, and Mik Kersten has revisited in Output to Outcome (2026) the shift he named in Project to Product (2018). Both reach a similar conclusion: AI accelerates what the organization already does, so the operating model matters more than before.

What's New

The skill keeps its seven blocks and its twenty-five topics, each with its own chapter in the development guide. The changes are distributed as follows:

  • Foundations: the APOM described through its four key areas (strategy, people, structure, and value cycle) and its four core principles, Kersten's reading, and the tension between outcomes and predictability.
  • The product and the portfolio: the APOM's definition of product, the differences between distinctive products and generic ones, and Scrum.org's six principles for the portfolio.
  • Structure: the end-to-end ownership of the empowered team, how AI reshapes the weight of competencies, and the second edition of Team Topologies (2025), which elevates cognitive load to a design principle.
  • Funding and governance: the twelve principles of Beyond Budgeting and outcome-based governance.
  • Metrics: the five DORA metrics and one evidence metric for each principle of the model.
  • Culture and transition: predictability as the root of many objections, the urgency that AI adds to the transition, and the boundary with scaling frameworks, now that some of them present themselves as operating models.

All topics have been reviewed against their sources, and the guide now links to fifteen pages of the Scrum Manager BoK.

Three Ideas the New Version Puts in the Spotlight

AI accelerates the model you already have. Kersten summed it up in April 2026, in words IT Revolution quoted: with the product model, AI accelerates doing the right thing, and with the project model, doing the wrong thing. Cagan noted in July that most organizations use AI to speed up their old project-based way of working. And DORA's 2025 report observes that AI improves delivery pace while also increasing instability. For that reason the guide presents delivery cadence as a necessary condition of the model, one that is not enough if teams do not get better at discovering what to build.

The rival of outcomes is predictability. In October 2026 Cagan clarified where the underlying tension lies. Outcomes need deliverables, so the real trade-off is between outcomes and predictability. Committing to dates and features gives a sense of control that outcomes cannot offer, because many product ideas will not work. The problem appears when an organization puts predictability first and leaves the outcome as a side effect of what was promised. The guide teaches how to recognize when this happens and why it sits at the root of many objections to the model.

Operating by product can be verified. An organization can have the full vocabulary of product and still operate by project. The guide proposes four questions to detect that cosmetic change: whether teams are assigned problems or solutions, whether funding is persistent or per project, whether investment is reviewed based on evidence or on milestones, and whether teams decide or committees approve.

The APOM's guiding principles also associate an evidence metric with each principle, such as the percentage of decisions that teams make without escalating them, and ask that flow metrics not be used to set individual targets. It is a recent proposal, still without a reference value, and we present it as such.

What We Have Corrected

A new version is also an opportunity to make corrections. When reviewing the first version against its sources, we have clarified:

  • The Scrum.org model. We described it with seven characteristics, its 2025 formulation, which remains as the initial formulation. Since January 2026 it is described by its guiding principles.
  • Cagan's model. We spoke of about twenty principles. There are twenty, grouped into five concepts (culture, strategy, teams, discovery, and delivery) and articulated across three dimensions.
  • The Beyond Budgeting principles, which now follow the enumeration in the Beyond Budgeting Institute document we cited: twelve, six on leadership and six on management processes.
  • Attributions. A sentence about AI that we attributed to Cagan is, in his article, from another person he quotes, so we have removed it. The linked source also did not support that Cagan calls the empowered team "the most fundamental concept" of the model; we now say he places it at the center. And the relationship between the APOM and SAFe was raised by Yuval Yeret in a Scrum.org podcast, so we present it as his reading and not as an institutional position.

Who It Is For and What It Certifies

It is a skill for those who lead or guide an organization's shift from projects to product: executives and product managers, Product Owners, Scrum Masters, agile coaches, transformation leads, and those who decide, from finance, how work is funded.

It covers the operating model and leaves out the detailed craft of each role (the Product Owner's has its own core certification in Scrum Manager) and the teaching of scaling frameworks. It complements other Skill Arena skills: OKRs and Product Strategy, which develops the objectives technique the model uses to align the portfolio and the teams, and Product Discovery and Customer Validation, which covers how to find out which solutions work.

The Skill Arena diploma certifies, among other competencies, the ability to distinguish product work from project work, to fund and govern by product, and to lead the transition to the model. The training and assessment banks have been fully regenerated from the new guide, at two difficulty levels.

The new version is available in Spanish and English.

How to Access It

The State of the art, the development guide, and the training and assessment platform are on the skill's page in Skill Arena: Agile Product Operating Model.

Read, train, and tell us what you think. Every contribution, criticism, or suggestion helps us prepare the next version.

Share:

Comments (0)