Agile Transition — learn from success, failure on Age-of-Product.com

The Jobs Matrix for AI: Four Boxes Instead of Forty Tools

by Stefan Wolpers | 2026-09-27 Featured Agile and ScrumAgile Transition

TL;DR: A 2×2 Matrix on AI for Agile Practitioners

You probably think making sense of AI means keeping up with every new tool, agent, and pricing tier. Steve Jobs faced a similar mess at Apple in 1997, with a dozen versions of the Macintosh, and he fixed it with a two-by-two grid on a whiteboard. Almost 30 years later, the “Jobs Matrix for AI” sorts the AI tool market and, more usefully, the AI use cases of Scrum Masters, Product Owners, Agile Coaches, and anyone else in agile product development.

Replace Consumer and Pro with Team and Organization, and Desktop and Portable with Chatbot and Agent, and you get four boxes that show where a use case belongs, what it takes to move it, and which box should stay empty.

The Jobs Matrix for AI: 4 Boxes Instead of 40 Tools for Agile Practitioners on Delegation and Judgment - Age-of-Product.com

Thesis: This article applies Steve Jobs’ 1997 Consumer/Pro, Desktop/Portable matrix first to the 2026 AI tool market, and then to agile practices, producing a 2×2 matrix that sorts AI use cases by required decision rights and by delegated authority.

AI on Top of a Dysfunctional System: The Product Backlog

by Stefan Wolpers | 2026-09-20 Agile and ScrumAgile Transition

TL;DR: Polished Artifacts, Unchanged Decisions, Or Ten Backlog Anti-Patterns AI Makes Worse

Add AI to a Product Backlog process that already struggles, and everything seems to improve within an afternoon. The problem is that polishing artifacts with AI doesn’t fix the root cause: the basis for the team’s decisions doesn’t change; AI only removes the visible discomfort that used to signal something was broken, along with some of the pressure to fix it. AI applied to a dysfunctional system – here, the Product Backlog process – makes the dysfunction look like progress.

This is the first article of a new series that explains the uselessness of bolting AI onto a dysfunctional system. It explains why generative AI worsens ten Product Backlog anti-patterns, how polished AI artifacts can hide missing evidence and authority, and how teams can check whether their process is fit for AI.

The example anti-patterns accelerated by AI are from my Scrum Anti-Patterns Guide book.

AI on Top of a Dysfunctional System: 10 Product Backlog Anti-Patterns AI Makes Worse – by Stefan Wolpers of Age-of-Product.com

Thesis: Adding AI onto a dysfunctional system, for example, the Product Backlog, makes ten typical backlog anti-patterns worse, because polished AI artifacts hide missing customer evidence, decision authority, and feedback; the article explains these mechanisms, their costs, and how teams test whether their process is ready for AI.

The AI Workflow Inventory: Can Your Team Name the Work It Already Runs With AI?

by Stefan Wolpers | 2026-09-13 Agile and ScrumAgile Transition

TL;DR: The AI Workflow Inventory Finalizes the A3 Delegation System

You probably know your own AI shortcuts: the colleague who drafts the stakeholder update, the nightly job somebody set up before they left, the interview notes that go through a model on demand. However, I want to challenge you: that perceived knowledge can create false confidence, because it feels like knowing the team’s way of working with AI, when it is still only a diffuse understanding of the practice. Ask the team to combine those individual accounts into one list, and you may discover how little of the whole anyone can see. The AI Workflow Inventory is the artifact for that list: one row per recurring task, refined into provisional task classes to prepare the team’s next AI delegation decisions.

This is another post from the series on building the A3 Delegation System in public. (I gladly answer all questions you have, and yes, I am considering creating an A3 Delegation application.)

The AI Workflow Inventory of the AI Delegation System: Can Your Team Name the Work It Already Runs With AI? - Age-of-Product.com

Thesis: The AI Workflow Inventory is a one-page canvas listing every recurring task a team already runs with AI, grouped into provisional task classes. It is A3 Delegation System’s seventh artifact. This article explains how to build it in one 60-minute session.

AI Transformations And Agile Transformations Rhyme

by Stefan Wolpers | 2026-09-06 Agile and ScrumAgile Transition

TL;DR: AI Transformations and Agile Transformations Rhyme

AI adoption seems to be scaling: 37% of respondents in McKinsey’s 2026 survey report an EBIT effect from AI, and Gartner finds that 22% of organizations have scaled it across business units. Now, Agile practitioners have seen this combination before, as AI transformations and Agile transformations rhyme. There are five classic failure patterns from the Agile transformation adventures that are back under new names: from mandates from above to licenses mistaken for training to greenfield showcases to parachuted consultants to promised payroll savings dressed up as strategy. They share one condition: organizations make AI decisions at organizational scale without leaving inspectable evidence at the workflow level in the trenches. And for good measure, let us throw in ignoring culture and excluding most of the organization’s people in the process.

The A3 Delegation System is not an AI-transformation method. It is a deliberately low-tech, paper-level discipline that lets a team produce that evidence in hours, and this article spends as much time on where the system stops as on what it does. If you are a Scrum Master, Product Owner or Manager, an Agile Coach, or a Project Manager who has to argue upward about AI, the last section gives you one thing to do this week.

AI Transformations And Agile Transformations Rhyme: The A3 Delegation System Is The Low-Tech Countermeasure – Age-of-Product.com

The Folly of Tokenmaxxing, or What AI Learns About Legacy Organizations That Agile Already Knows

by Stefan Wolpers | 2026-08-16 Agile and ScrumAgile Transition

TL; DR: Tokenmaxxing Or Reinventing the Wheel

Your organization counts AI tokens, seats, and pilots, but can anyone name a single decision those numbers actually changed? Tokenmaxxing is only the symptom; five old Agile Laws explain the cause, and each one comes with a test you can run this week. There is no need to reinvent the wheel with AI transformations and learn the hard way what the veterans of other transformations already figured out.

The Folly of Tokenmaxxing, or What AI Learns About Legacy Organizations That Agile Already Knows - Age-of-Product.com

Thesis: Tokenmaxxing is the vanity metric of pushing low-value work through an AI tool solely to inflate usage metrics. Tokenmaxxing emerged in 2026, when large technology companies began ranking employees by token consumption on internal leaderboards. The behavior is rational for the individual but useless for the organization because tokens measure input rather than outcomes. The five Agile Laws in this article explain why organizations keep making this mistake and what to measure instead.

From Agile to the Product Operating Model: What Practitioners Say Is Actually Changing

by Stefan Wolpers | 2026-08-10 Featured Agile TransitionLean and Product

TL; DR: The “Agile to the Product Operating Model” Survey Results

Between August 2 and August 10, 2026, 48 practitioners participated in my Agile to Product Operating Model (POM) survey, which tries to shed light on what is actually changing.

Let me summarize the answers for you: the reported transformations change decision-making less than the Cagan framework suggests. Where respondents report improvements, they appear in delivery and collaboration rather than in business results. Unfortunately, the human side of the transition is the least encouraging part of the answers.

Take all the following information with a grain of salt, given that the sample size is so small. (I recall the good times when 1,000 to 2,000 people would participate in a Scrum master salary report, but those times seem to be over, despite my asking 39,000 people for their contributions via a newsletter.)

Agile to the Product Operating Model Survey Results: What Practitioners Say Is Actually Changing – Age-of-Product.com

Thesis: Product operating model transformations mostly change vocabulary and organizational structure while leaving the decision system, who decides what gets built, on what evidence, at what speed, largely untouched. AI is changing product decisions independently of POM transformations.