đ Free e-book: The 7 success factors of software testing. 25 years of project experience in one 33-page workbook, now also in English đ Get it for free
"There actually is no agile manifesto." - Michael Mahlberg
What happens to the teams and organizations left behind after an agile transformation that didn't deliver what it promised? With Michael Mahlberg I talk about why the word "agile" has lost its meaning, how big consultancies pushed companies deeper into rigid structures under an agile label, and what it actually takes to help an organization find its footing again. We get into the question of what genuinely worked from the last 25 years, from fast iterations and real customer feedback to decision-making practices borrowed from outside the agile world entirely. What stays with me is Michael's point that arguing for change rarely works, but pulling people into the experience of what isn't working just might.
Michael Mahlberg has been supporting clients in organizational development with lean approaches, light weight processes, systemic organizational development, and Kanban, since the 1990s. He was co-founder of the Cologne-based "Limited WIP Society" and speaks regularly at conferences. His focus is on the helpful use of these methods at personal team, and organizational level, accompanied by his mantra: Accept Reality.
https://mastodon.online/@MMahlberg
Highlights:
- The Agile Manifesto is a manifesto for agile software development only, not for agile management or organizational leadership, yet companies applied it as if it covered all of those.
- Applying a fixed framework like SAFe pushes differentiation-phase companies deeper into rigid role structures rather than helping them adapt, because it copies organizational blueprints instead of developing fitting solutions.
- Fast iterations and genuine customer feedback are practices from the agile era that still hold value, but most organizations claiming to run agile no longer collect real feedback because they delay rollout.
- Arguing with management about dysfunction triggers automatic defensiveness, and the more a position is defended, the more the defender believes it, making direct argument counterproductive.
More Links with Insights:
Fler avsnitt av Software Testing Unleashed - QA, DevEx & Quality Engineering
Visa alla avsnitt av Software Testing Unleashed - QA, DevEx & Quality EngineeringSoftware Testing Unleashed - QA, DevEx & Quality Engineering med Richard Seidl | Software Development & Testing Expert finns tillgÀnglig pÄ flera plattformar. Informationen pÄ denna sida kommer frÄn offentliga podd-flöden.
