by Stefan Wolpers|FeaturedAgile 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.
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.
by Stefan Wolpers|FeaturedAgile 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.)
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.
Your team already delegates work to AI: reports, research, customer feedback analysis, stakeholder communication, or parts of operational workflows.
But can you answer these questions without improvising?
What may AI decide, and what must remain a human decision?
What does “good enough” mean for this particular work?
Who verifies the result before somebody acts on it?
Who checks whether the delegation still works after the model or workflow changes?
If those answers live in one person’s head, or nowhere, your problem is no longer prompting. You have a delegation problem.
The A3 Delegation System gives you a practical way to decide what AI may do, hand over the work clearly, define acceptable results, and inspect the delegation over time.
During two hands-on sessions, you will apply the system to a workflow. You will leave with a clear understanding of how to apply the A3 Delegation System to your workflows so that team members or stakeholders can understand, challenge, and continue your AI delegation work. Everything you learn is directly applicable to your situation the next day. The class is in English.
You learned to prompt, and your organization learned to spend. Unfortunately, few organizations have learned to connect the two. That is where the AI4Agile online course comes in.
An AI operating capability exists when delegated work can be reproduced without its original creator, meets an explicit quality standard, follows a defensible execution path, has a named owner, and is inspected often enough to detect drift. The AI4Agile Online Course V3 teaches practitioners how to build one, independent of a particular AI model, and still, there is no coding required. The course is in English. 🇬🇧
by Stefan Wolpers|FeaturedAgile and ScrumAgile Transition
Using AI at Work Does Not Mean You Understand It
Many agile practitioners use ChatGPT at work. That does not mean they understand AI well enough to trust your own judgment. The problem is not that agile practitioners ignore AI. The problem is that many already use it confidently without knowing where their judgment breaks down. The free AI4Agile Foundational Assessment measures precisely this skill gap. (Download your access file below.)
The assessment comprises 40 scenario-based questions. It does not ask for definitions, but puts you into situations that agile coaches, product managers, and Scrum Masters face every week: weak prompting producing generic output, misleading data analysis, questionable agent output, and, possibly, organizational pressure to treat AI output as “good enough” to go with it.
Most people who use AI do not fail because they lack knowledge, but because they cannot distinguish between plausible outputs and trustworthy judgment. But see for yourself!
by Stefan Wolpers|FeaturedAgile and ScrumAgile Transition
TL;DR: The A3 Handoff Canvas
The A3 Framework helps you decide whether AI should touch a task (Assist, Automate, Avoid). The A3 Handoff Canvas covers what teams often skip: how to run the handoff without losing quality or accountability. It is a six-part workflow contract for recurring AI use: task splitting, inputs, outputs, validation, failure response, and record-keeping. If you cannot write one part down, that is where errors and excuses will enter.
The Handoff Canvas closes a gap in a useful pattern: from an unstructured prompt to applying the A3 framework to document decisions with the A3 Handoff Canvas, to creating transferable Skills, potentially leading to building agents.
by Stefan Wolpers|FeaturedAgile and ScrumAgile Transition
TL; DR: The A3 Framework
The A3 Framework categorizes AI delegation before you prompt: Assist (AI drafts, you actively review and decide), Automate (AI executes under explicit rules and audit cadences), or Avoid (stays entirely human when failure would damage trust or relationships). Most AI training teaches better prompting. The A3 Framework teaches the prior question: Should you be prompting at all? Categorize first, then prompt.
by Stefan Wolpers|FeaturedAgile and ScrumAgile Transition
TL; DR: Why the Brand Failed While the Ideas Won
Your LinkedIn feed is full of it: Agile is dead. They’re right. And, at the same time, they’re entirely wrong.
The word is dead. The brand is almost toxic in many circles; check the usual subreddits. But the principles? They’re spreading faster than ever. They just dropped the name that became synonymous with consultants, certifications, transformation failures, and the enforcement of rituals.
You all know organizations that loudly rejected “Agile” and now quietly practice its core ideas more effectively than any companies running certified transformation programs. The brand failed. The ideas won.
TL; DR: The Scrum Master Interview Guide to Identify Genuine Scrum Masters
In this comprehensive Scrum Master Interview guide, we delve into 97 critical questions that can help distinguish genuine Scrum Masters from pretenders during interviews. We designed this selection to evaluate the candidates’ theoretical knowledge, practical experience, and ability to apply general Scrum and “Agile “principles effectively in real-world scenarios—as outlined in the Scrum Guide or the Agile Manifesto. Ideal for hiring managers, HR professionals, and future Scrum teammates, this guide provides a toolkit to ensure that your next Scrum Master hire is truly qualified, enhancing your team’s agility and productivity.
If you are a Scrum Master currently looking for a new position, please check out the “Preparing for Your Scrum Master Interview as a Candidate” section below.
So far, this Scrum Master interview guide has been downloaded more than 25,000 times.
TL; DR: 92 Product Owner Interview Questions to Avoid Imposters
If you are looking to fill a position for a Product Owner in your organization, you may find the following 92 interview questions useful to identify the right candidate. They are derived from my sixteen years of practical experience with XP and Scrum, serving both as Product Owner and Scrum Master and interviewing dozens of Product Owner candidates on behalf of my clients.
So far, this Product Owner interview guide has been downloaded more than 10,000 times.
TL; DR: Upcoming AI 4 Agile Workshops, Scrum Training Classes, and Events
Age-of-Product.com’s parent company — Berlin Product People GmbH — offers Scrum training classes authorized by Scrum.org, Liberating Structures workshops, and hybrid training of Professional Scrum and Liberating Structures. The training classes are offered both in English and German.
Check out the upcoming timetable of training classes, workshops, meetups, and other events below and join your peers.
TL; DR: AI Pace Accelerating — Food for Agile Thought #564
Welcome to the 564th edition of the Food for Agile Thought newsletter, shared with 35,278 peers. This week, Simon Willison suggests that the current AI pace exceeds even his predictions, while Jenny Wanger believes it has made the product trio single-player, creating product debt in the process. Dan Shipper proposes a labs team expecting to discard 90% of its work, whereas Teresa Torres and Petra Wille treat innovation as a byproduct, not a goal. Ben Thompson suggests whoever owns your agent becomes the ultimate gatekeeper, yet Madeline Renbarger, M. Sriram, and Tom Dotan report even agentic commerce enthusiasts still want control.
Next, Dror Poleg suggests delegation ties his AI glossary together, and Casey Newton shows its price: OpenAI’s Dots saves him two hours but wants your email and bank account. For delegated code, Addy Osmani fears that the engineer approving it without independent checks becomes the moral crumple zone. Arvind Narayanan and Sayash Kapoor propose AI extinction probabilities are guesses wearing numbers, whereas Paweł Huryn’s analysis of AI subscription benefits rests on API list rates: SuperGrok buys 190x its price.
Lastly, John Cutler suggests your virtues lure you into career traps, while Jonny Miller points out that white-knuckled grinding ends in burnout; let go. Tim Ottinger hopes AI kills ticket culture and revives XP, whereas Viktor Cessan proposes automating internal requests only once volume justifies it. Finally, Fran Noto favors pairing over documentation; the latter captures only a fraction of what experienced people know, and Anuja Karnik and Sumeet Gayathri Moghe suggest trust grows in everyday work, not by orchestrated events.
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.
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.
TL; DR: Survival of High-impact Ideas — Food for Agile Thought #563
Welcome to the 563rd edition of the Food for Agile Thought newsletter, shared with 35,293 peers. This week, Jason Knight and Rich Mironov explore why faster AI-generated code does not create faster revenue, and Itamar Gilad sees a similar limit: output-maxing won’t rescue high-impact ideas from prioritization politics. John Cutler believes AI strips the positive friction forcing teams to think, while Roman Pichler suggests its sprawl lets teams hit targets as the business stagnates. Martin Eriksson would assumption-map leadership’s untested strategy, whereas Pavel Samsonov believes “Claude wrote it” launders slop.
Next, Artificial Analysis finds Claude Opus 5.5 tops its Intelligence Index, while Simon Willison reports that Opus on “Max” thinks so hard it never delivers the Pelican, Simon’s famous test. Addy Osmani suggests deleting “think carefully” prompts and naming when to stop. Diogo Almeida wants models to return typed decisions instead of text, creating Jev, while Charity Majors suggests chatbot answers erode trust when colleagues want your opinion. Also, Mustafa Suleyman believes Anthropic’s constitution fuels anthropomorphism and makes containing AI harder.
Lastly, Nigel Thurlow and Mike Fisher learn from Toyota: Thurlow believes AI visibility changes nothing unless leaders act, while Fisher shows performance is largely systemic. Tim O’Reilly likewise believes going AI native is a human problem. Steve Blank watched day-one AI demos turn MVPs into evidence theater, and James Shore believes AI speed gains can evaporate. Finally, Jeff Gothelf suggests key results track the humans deploying or receiving an agent’s work, not API calls.
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.
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.
TL; DR: Slop Grenades — Food for Agile Thought #562
Welcome to the 562nd edition of the Food for Agile Thought newsletter, shared with 35,321 peers. This week, Tobi Lütke tells Shane Parrish that AI makes judgment more valuable because machines cannot take responsibility. Teresa Torres, Petra Wille, and Josh Elman add that AI cheapens features and demos, yet working products still demand judgment. Barry O’Reilly makes that judgment auditable before deployment through baselines and accountable owners. Also, Dario Amodei applies that accountability to the labs with third-party evaluators and speed limits, while Dwarkesh Patel’s guests expect expert-beating AI within ten years.
Next, Nigel Thurlow argues that we turned Lean into belts and templates, although Toyota wanted a better management system. Refinement repeats that mistake: Maarten Dalmijn untangles its four parallel conversations, and Mike Cohn warns that polished AI stories hide gaps. AI adoption needs the same management focus: Aaron De Smet ties it to trust, Christiaan Verwijs and Barry Overeem recruit volunteers for Reflexive AI, Addy Osmani explains how unsupervised agents turn legacy code into technical debt factories.
Lastly, Cedric Chin argues that structural constraints, not stubbornness, kill incumbents, and Elena Verna catalogs the sales habits that smother PLG. Matthew Hodgson applies that logic to AI, where functional silos swallow productivity gains unless leaders fix the operating model before buying tools. Also, Eliezer Yudkowsky explains why models ignore instructions: a polite ambassador talks while a doer chases rewards. Finally, Marily Nika plans for that gap with Minimum Viable Quality: rank failure modes and design for recovery.
