TL; DR: Reusing Agile Artifacts to Avoid Accumulating AI Debt
In this video from the 76th Hands-on Agile Meetup, I walk you through the A3 Delegation System and show how it helps avoid AI debt by borrowing artifacts and practices from Agile, such as the Definition of Done and Retrospectives. If you’d like to download the corresponding canvases (the artifacts of the A3 Delegation System), you can do so below.
You will get a full set of PDFs, along with the guide to the A3 Delegation System, so that you can run the system with your own teams. Enjoy the video and let me know whether you consider the A3 Delegation System useful.
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. 🇬🇧
Your Claude Pro subscription hits limits faster than it did in January, as Anthropic quietly re-priced the ceiling, and every AI provider is rationing compute. If you keep working with Claude the way you did six months ago, you are in for a rude awakening. This article gives you four principles that explain how Token Economics actually works, so you can stop accepting the black box and start using your budget deliberately.
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: 82 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 82 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: Scrum Training Classes, Liberating Structures Workshops, 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: Toyota Production System — Food for Agile Thought #554
Welcome to the 554th edition of the Food for Agile Thought newsletter, shared with 35,428 peers. This week, Nigel Thurlow presents the Toyota Production System (TPS) as a disciplined whole, a lesson Pavel Samsonov and Ash Maurya extend to product work: faster AI delivery only magnifies incoherence without workflow thinking, customer evidence, and validation. Zvi Mowshowitz shows the darker side of unchecked AI optimization, while Steve Newman questions its societal impact to date. Barry O’Reilly ties these concerns to leadership, urging redesign of workflows, judgment, decision rights, and accountability before scale amplifies weak systems. (Again, history rhymes; remember “Agile?”)
Next, Leah Tharin reframes activation as the full path from first touch to lasting habit, a view that challenges vanity metrics. Also, Michele Zanini and Gary Hamel question inflated AI claims, and Zanna Iscenko and Scott Strand add evidence of broad but shallow adoption. Chris Chinchilla’s Nokia history warns of what happens when execution lags behind change, and Johanna Rothman brings the remedy to focus: visualize work, expose delays, finish one thing, and reject the rest.
Lastly, Ant Murphy separates strategic leverage from strategy labels, while Steven Sinofsky argues that restricting AI model distillation would entrench incumbents, when more competition should be the goal. David Burkus turns to management, showing how leaders can shield teams from chaos without hiding uncertainty. Addy Osmani warns that AI-automated code creates comprehension debt, and John Cutler connects the themes: AI succeeds only when teams understand the work, retain human judgment, and trust leaders not to weaponize productivity gains.
TL; DR: Dangerous Agile Myths — Food for Agile Thought #553
Welcome to the 553rd edition of the Food for Agile Thought newsletter, shared with 35,462 peers. This week, Henrik Mårtensson dismantles seven dangerous Agile myths, showing that fat-tailed cycle-time data invalidates the use of story points. Teresa Torres and Petra Wille question whether support tickets can replace story-based interviews, while Roman Pichler pushes visions beyond feature lists toward purpose. Turning to AI, Laura Summers finds LLM-assisted coding replaces building satisfaction with supervision fatigue, Benedict Evans sees foundation models becoming commodities, and Satya Nadella urges firms to own their learning loops before providers capture proprietary knowledge.
Next, John Cutler reframes software assets through a portfolio lens, asking whether AI makes you faster or moves you faster in the wrong direction. George Sivulka and Arvind Narayanan both place the bottleneck in management, not model capability. On the human side, Sean Goedecke redefines engineering politics as knowing who holds power and making contributions visible, while Steven Sinofsky compares Chicago Law School’s AI ban to Harvard’s 1982 computer ban, arguing such restrictions never last.
Lastly, Pavel Samsonov argues that product empathy rings hollow without respect, a gap LLMs deepen by pushing error correction onto users. Thomas Squeo and Matt Kamelman trace enterprise AI failure to missing governance, not weak models. Susan MacKenty Brady, Stuart Kliman, and Leslie Smith name four leadership traps quietly eroding trust. Finally, Dave Rooney rethinks story slicing when AI handles large tasks, and Tristan Kromer notes AI accelerates experiments but cannot pick the right question.
Your team already has rules for using AI. Some live in templates, some in habits, exceptions, and one person’s memory. The AI Working Agreement puts the decisions that matter in one place: what the team delegates to AI, what stays human, what must be reviewed, what never enters a model, who owns which workflow, and how the agreement changes. Write it, and a new colleague can read your team’s AI decisions on their first day, while the decisions stay when someone leaves.
Thesis: Team-level AI governance fails more from uncodified judgment than from missing policies. The AI Working Agreement turns scattered AI decisions into one inspectable artifact, so a team can onboard people, survive departures, and challenge its own habits before those habits harden into risk.
