Agile and Scrum: Learn about agile frameworks on Age-of-Product.com

We’re Not Paid to Practice Scrum, but Answer 5 Product Questions

by Stefan Wolpers | 2026-11-08 Featured Agile and ScrumAgile Transition

TL;DR: Cheap Code Makes 5 Product Questions Expensive to Skip

Thesis: This article explains five product questions that become more consequential when AI makes software implementation cheap, why falling AI costs increase the volume of work those questions must filter, and how teams set working principles during early AI adoption.

For decades, the cost of building software rationed what an organization could start: nobody could afford to build everything, so somebody had to choose, however crudely. AI has weakened that rationing; the frontier labs need your organization to use more AI with every model generation, and the product operating model promises to fix what Agile supposedly broke. None of this guarantees that anyone asks whether the work solves a customer problem, nor whether solving it was worth the cost. You need to address these product questions yourself.

These product questions become more expensive to skip when starting work gets cheap: which problem is worth solving, whether the work is the best use of the team’s time, whether it is good enough for the people who will see it, whether it solved the problem, and whether the team’s way of working still fits. AI agents can prepare evidence under the A3 Framework’s Assist category, where the agent analyzes and people decide, while explicit standards for AI-assisted work, such as the AI Definition of Done, and recurring inspections, such as the AI Delegation Audit, keep the answers honest. Whether you call any of this Scrum is the least interesting question of all.

We're Not Paid to Practice Scrum, but Answer 5 Product Questions: When AI makes software implementation cheap - Age-of-Product.com

Measuring AI Impact: What Your Velocity Chart Cannot Tell the CFO

by Stefan Wolpers | 2026-11-01 Featured Agile and ScrumAgile Transition

TL;DR: What Your Velocity Chart Cannot Tell the CFO

Sooner or later, someone in your organization shows a slide with a number about what AI did for your team: typically, the team’s “velocity” before and after the coding agents arrived, plus a percentage that looks like a return on the token bill. The number may even be “correct”; however, it answers a different question than the one finance is asking: A before-and-after comparison credits every change in that period to the agents, and measuring velocity is controversial for good reason under normal circumstances, which makes measuring AI impact by this means even more challenging.

A claim your team can defend starts elsewhere: with an honest grade of the evidence, a break-even test for every delegated AI workflow, and the creep check of the AI Delegation Audit, which catches the workflows that pass the test only because nobody reviews their output anymore. Each workflow then gets a keep, change, or retire decision in the Re-classification Log, and the result fits on one page that states what the team can claim and what it cannot. Bonus: For your own work, a small trial of eight to ten runs gives you a direction you can act on.

📺 Watch the article’s video: Measuring AI Impact: What Your Velocity Chart Cannot Tell the CFO.

Measuring AI Impact: What Your Velocity Chart Cannot Tell the CFO - by Stefan Wolpers of Age-of-Product.com.

Thesis: This article explains how agile teams can measure AI impact effectively, why before-and-after velocity charts mislead, the three grades of evidence, a break-even test for delegated workflows, a one-page statement for finance, and a personal trial.

AI-Assisted Refinement Preparation

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

TL; DR: The Product Backlog Refinement Agent and the Risk When a Suggestion Becomes a Decision

Preparing a refinement session is tedious, and AI is good at the tedious part: reading every Product Backlog item, every repeated comment column, and the team’s own records on the afternoon before. The risk sits elsewhere. A refinement agent asked to “help with refinement” can take the conversation away from the team without writing a single acceptance criterion: “suggesting” to the Product Owner or Product Manager which items to close, merge, split, or create is enough, and the questions the team was supposed to work out arrive in the brief already answered.

The remedy is a boundary decided before the first run: the agent marks evidence and asks questions, the Product Owner checks the brief and sets the agenda, and the team refines. Writing that boundary into an A3 Handoff Canvas, together with what the agent reads and who checks its output, turns a good intention into a rule the agent follows and the Product Owner can verify.

📺 🇬🇧 Watch the video now: AI Refinement Prep Traps and How to Avoid Them.

The Refinement Agent and the Risk When a Suggestion Becomes a Decision – by Stefan Wolpers of Age-of-Product.com

Thesis: This article explains how Product Owners and Product Managers can use AI to prepare Product Backlog refinement without pre-empting the team’s conversation: four evidence checks, a four-part test separating suggestions from decisions, written boundaries, and human verification of the agent’s brief.

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.