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.
You moved your routine AI work to a cheaper model, so you think the cost question is handled; however, often, that is not the case. The decision lives in one person’s head and produces nothing that the person accountable for the invoices can read. Worse, it is an architectural choice nobody documented. The AI Routing Policy is the missing artifact of Stage 2 of the Delegation Lifecycle: it records which execution path, from a cheaper model to a frontier model to plain code, handles each class of work, what counts as good enough output to meet the AI Definition of Done, and who owns the call. The skill it needs to work is one you already have: You write acceptance criteria.
Thesis: An AI routing policy is not about picking a cheaper model at the moment of executing an AI task. It is a written, repeatable team decision that assigns each task class to the cheapest sufficient execution path: a model, human review, deterministic code, or no automation. Paired with a minimal routing log, it creates the spend-by-task-class record that your finance team will eventually request. You can draft the first three lines in twenty minutes.
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: AI Creates Jobs? — Food for Agile Thought #552
Welcome to the 552nd edition of the Food for Agile Thought newsletter, shared with 35,468 peers. This week, Ramp Economics Lab and Revelio Labs report that heavy AI adopters grew headcount by 10%, yet Charity Majors insists only honest feedback loops turn adoption into results. Alex Karp questions the economics entirely, calling token pricing fundamentally broken. Pavel Samsonov and Jerry Colonna both argue that speed without trust or judgment produces waste, while Janna Bastow reminds us that roadmap dates are comfort objects that mask the need for outcomes.
Next, Jeff Gothelf proposes that when AI makes building nearly free, teams should prioritize learning value and reversibility over effort. Kyle Poyar believes the resulting cost crisis is self-inflicted and offers a five-step spending fix. Yanli Liu warns that even working tools like Claude Skills silently rot without maintenance, while Addy Osmani suggests engineers must own accountability as agents handle execution. Also, John Cutler recommends that overthinkers disconnect self-worth from work entirely.
Lastly, Paweł Huryn frames the 2026 AI PM roadmap around whether agents run on your work or inside your product, while Alberto Romero raises a stranger question: why do AI models keep inventing their own languages? Fabian Metzeler and McKinsey colleagues distill seven truths from 15 AI-native companies, yet Cris Beswick warns most transformations stall when organizations skip differentiated innovation. Finally, Ant Murphy proposes a two-question test to tell actionable metrics from noise.
TL; DR: AI Confidence Theater — Food for Agile Thought #551
Welcome to the 551st edition of the Food for Agile Thought newsletter, shared with 35,473 peers. This week, Elena Verna calls out AI confidence theater and asks teams to show real workflows, which pairs well with Teresa Torres and Petra Wille’s advice to start AI adoption with one messy to-do item. Also, Janna Bastow brings the same discipline to alignment meetings: clarify decisions before vague input becomes commitment. Anthropic frames Fable 5’s return as governance, while Alberto Romero questions the safety bargain, and Mike Cohn redirects failed Agile blame toward broken conditions.
Next, Aakash Gupta and Shubham Saboo treat PM work like code, while Hamel Husain extends that discipline to AI evaluation: track changes, show provenance, and make review paths obvious, and Tomasz Tunguz adds the cost pressure that will force selective adoption. Joost Minnaar reminds teams that rituals without shared power rot into theater, and Anthropic frames Claude Fable 5 as a teammate needing clearer boundaries.
Lastly, Ethan Mollick sees AI work shifting toward agent management, while Peter Yang expects model portfolios to reshape software economics. Charity Majors argues that leaders must support learning rather than demand unpaid adaptation, and Gergely Orosz reminds us that reinvention beats nostalgia. Finally, Abraham Thomas ties lasting progress to data quality that delivers real business outcomes by matching fitness for purpose with measurable value rather than relying solely on checklists.
Scrum teams inspect how the last Sprint went during the Retrospective. They are much less likely to inspect the work they have handed to AI, because no meeting on the calendar owns it. That gap is where a working AI automation quietly turns into risk: it keeps producing fluent, on-brand output long after the decision to trust it has expired. The AI Delegation Audit closes the gap by leveraging the facilitation skills teams already use in a Retrospective.
Thesis: The Delegation Audit is the missing inspection cadence for delegated AI work. It checks four things: whether the work still meets the standard, whether the model still fits the task, whether the team can still stop the automation, and whether reviewed assistance has quietly become unreviewed automation. You can try it on one workflow in fifteen minutes.
TL; DR: Make AI Boring — Food for Agile Thought #550
Welcome to the 550th edition of the Food for Agile Thought newsletter, shared with 35,481 peers. This week, Charity Majors rejects AI purity theater and urges disciplined workplace experiments, just make AI boring again, while Gojko Adzic warns that faster builders without product judgment will ship polished waste. Dave Hora names the organizational traps that keep teams from seeing reality, and Johanna Rothman brings the fix down to flow data and human judgment. Azeem Azhar and colleagues see AI demand rising, but Satya Nadella argues that a durable advantage comes from owning learning itself.
Next, Paweł Huryn moves AI work from prompt craft to agent loops with goals, guardrails, budgets, and independent checks, while Jeff Gothelf argues that AI pilots fail when firms bolt tools onto stale workflows. Joe Hudson adds that emotional clarity now beats knowledge hoarding, and John Cutler names fear, incentives, and executive fantasies as the real bottlenecks. David Burkus brings the pattern back to procrastination, where stress and ambiguity demand clarity without control.
Lastly, Elena Verna pushes experimentation beyond tiny UI tweaks toward larger monetization bets and longer engagement signals, as Zvi Mowshowitz warns AI policy needs calibrated safeguards rather than theater. Deborah Rim Moiso brings the same discipline to facilitation through communities that review real work, and Olivier Wulveryck applies Team Topologies to agentic platforms before shadow IT hardens. Finally, Itamar Gilad grounds the pattern in value, not misleading productivity counts.
