The Agile Manifesto followed Luther’s Reformation arc: radical simplicity hardened into scaling frameworks, transformation programs, and debates about what counts as “real Agile.” Learn to recognize when you’re inside the orthodoxy and how to practice the principles without the apparatus.
This is Part 2 of a three-part series; check out Part 1: Agile Is Dead, Long Live Agility.
Welcome to the 523rd edition of the Food for Agile Thought newsletter, shared with 35,802 peers. This week, Addy Osmani reflects on 14 years at Google, showing how user focus, clear thinking, and steady learning are true career success factors. Janna Bastow pushes back on traditional roadmaps, urging teams to ditch false certainty in favor of action-based planning. Elena Verna and Jonathan Yagel make the case for Building in Public as a trust-building engine. Meanwhile, technicalities warns of uneven AI progress, and Tim Tully et al. see a durable AI boom shaping enterprise adoption.
Next, Roman Pichler urges product teams to lead themselves, stressing shared ownership, clear authority, and skilled coaching. Joshua Seiden reframes AI-savvy product managers as translators, not engineers. OpenAI launches GPT-5.2, highlighting faster reasoning, vision, and tool use. Gavin Baker and Patrick O’Shaughnessy break down AI infrastructure ROI as a game of tokens, cycles, and execution. Shreyas Doshi demystifies micromanagement by showing when it blocks progress and when it clarifies expectations.
Then, OpenAI highlights a widening performance gap as enterprise AI adoption deepens. John Cutler urges teams to map real operating dynamics rather than cling to neat hierarchies. Cris Beswick warns that innovation needs intentional slack, not overworked teams, and Peter Yang offers practical tips for generating consistent, brand-aligned AI visuals. Finally, Erik Thorsell breaks down why estimates frustrate developers and matter to product owners, calling for transparency over false precision.
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.
So why are we still fighting about the label?
Welcome to the 522nd edition of the Food for Agile Thought newsletter, shared with 35,812 peers. This week, Gary Marcus questions the viability of large language models, citing unresolved flaws such as hallucinations and weak reasoning — Quo Vadis AI? Teresa Torres and Petra Wille reflect on AI’s role in user interviews, warning that tech cannot replace skilled human insight, while Peter Yang sees the PM role in AI-native firms shifting toward builders who align quickly. Also, OpenRouter’s massive token data analysis reveals rising agentic use and open models, and Willem-Jan Ageling dissects why many corporate transformations still stall.
Next, Dave Baines urges product managers to stop hiding technical work and instead align it through transparency and joint prioritization. Chris Jones and Marty Cagan remind stakeholders that their job is not to demand features but to enable outcome-driven problem solving. Saffron Huang’s team finds Claude changes engineering workflows at Anthropic and raises career questions. Also, Teresa Torres shares 50 AI use cases from her own process, and Eric Barker recommends strategy over emotion when dealing with difficult coworkers.
Then, Jing Hu questions the true ROI of AI investments, citing McKinsey data showing limited gains and weak agent adoption. Mike Brock calls AGI from LLMs a flawed idea dressed as progress. Mike Fisher warns that chasing velocity without slack leads to chaos, Martin Eriksson urges teams to simplify decisions through focus and consent, and Andi Roberts challenges Tuckman’s model. Finally, John Cutler explains why tools fail when they don’t tackle underlying behavioral constraints.
Your Agile events aren’t failing because people lack training. They’re failing because your organization adopted the rituals while rejecting the transparency, trust, and adaptation that make them work. And often, the dysfunction of mechanical ceremonies isn’t a bug. It’s a feature.
Welcome to the 521st edition of the Food for Agile Thought newsletter, shared with 35,803 peers. This week, Addy Osmani challenges engineers to sharpen critical thinking using a structured questioning approach to stay focused in AI-enhanced workflows. David Pereira cautions product managers against chasing AI tools at the expense of core skills like decision-making and alignment, and Martin Casado shares hard lessons from building new markets, from pricing mistakes to scaling traps. Grant Harvey recaps Ilya Sutskever’s view that scaling has peaked. Meanwhile, the 18th State of Agile Report signals a return to outcome-driven agility.
Next, Itamar Gilad outlines four product discovery models that balance control, creativity, and evidence, while Teresa Torres and Petra Wille explore how emotional recovery supports resilience in product teams. Simon Willison evaluates Claude Opus 4.5, noting its strength but also the blurring lines between top models. Johanna Rothman links flow metrics to culture change through storytelling, and Andi Roberts presents a hands-on framework to help teams align mindset, mechanics, and routines for better performance.
Then, Stuart Williams explains how AI shifts critical thinking toward context and judgment. Zvi Mowshowitz critiques Gemini 3 Pro’s confident errors. Allan Kelly says Agile evolves beyond hype, John Cutler explores cognitive style clashes in teams, and William Hudson warns against mixing up personas. Finally, Laura Tacho rejects activity metrics and proposes an outcome-focused framework for evaluating developer performance.
