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

AI-Assisted Product Discovery: When Code Is Cheap, Judgment Is the Job

by Stefan Wolpers | 2026-10-18 Featured Agile Transition

TL; DR: Deciding What to Build Is the New Job, Now that Code Is No Longer a Constraint

Agentic coding has removed the cost gate that used to stop product teams from chasing every idea at once, and the constraint has moved to product judgment: the ability to tell what is worth building. AI-Assisted product discovery can prepare that judgment by reading far more customer evidence than any product person could. Such a discovery agent analyzes three families of sources, checks eight patterns, and argues both against and for your current direction.

The A3 Framework has a name for this work: Assist, the agent analyzes and prepares, and the humans decide. The framework also helps to define the agent limits with the A3 Handoff Canvas – what the agent does, what the human does, which data we use, etc. – and the AI Definition of Done – what a quality AI output “looks like” – before the first run.

AI-Assisted Product Discovery: Deciding What to Build Is the New Job, Now that Code Is No Longer a Constraint - Age-of-Product.com

Thesis: This article on AI-assisted product discovery explains how product teams can use AI agents to compare customer feedback, usage data, and stakeholder requests with their product vision, product goal, product roadmap, and past decisions, flagging drift, bias, and sunk costs, while humans keep the decision under the A3 Framework’s Assist category.

To Switch, or Not to Switch the AI Model

by Stefan Wolpers | 2026-10-11 Agile and ScrumAgile Transition

TL;DR: The Hidden Cost of Switching AI Models

A new AI model arrives that is cheaper per token, scores better on benchmarks, and seems to require nothing more than a setting change. However, the token bill shows only part of the cost of switching AI models. There is also the effort to check whether your workflows, for example, the one to create status reports for stakeholders, still produce outputs in line with your AI Definition of Done. More often than not, this task remains unaligned with the decision to switch AI models.

In the worst case, switching AI models behind a business workflow can raise operating costs despite cheaper tokens, because business cases can miss the revalidation effort.

📺 🇬🇧 Watch the video of the article now: Before You Switch the AI Model: The Hidden Cost of ‘Updating’ Models.

Thesis: This article explains the recurring operational cost of switching AI models behind a business workflow: why the revalidation effort may disappear from upgrade decisions, how to screen a switch, and how Agile teams use an AI Definition of Done, test evidence, and an accountable owner to stay in control.

To Switch, or Not to Switch the AI Model, or: The Hidden Costs of Switching AI Models - by Stefan Wolpers, Age-of-Product.com

How to Catch AI Delegation Drift Before Your Board Does

by Stefan Wolpers | 2026-10-07 Agile and ScrumAgile Transition

TL;DR: The AI Delegation Audit Webinar Recording

When AI-assisted output still looks fine, it is tempting to conclude the delegation is fine. In my October 6 webinar with Scrum.org on the AI Delegation Audit, I walked through a fictional case in which that belief held for months, then fell apart in a board meeting, and showed the check that would have caught it.

How to Catch AI Delegation Drift Before the Board Does: The Recording of the AI Delegation Audit Webinar - Age-of-Product.com

Thesis: The AI Delegation Audit is a 45- to 60-minute review in the A3 Delegation System, run like a Sprint Retrospective, that checks whether a team’s AI delegations still hold; the post explains its four checks with a fictional case and shares the Scrum.org webinar recording.

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

by Stefan Wolpers | 2026-09-27 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.