Agile Micromanagement — Seriously? Making Your Scrum Work #27

TL; DR: Agile Micromanagement

There are plenty of failure possibilities with Scrum. Indeed, given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, the Scrum Guide clearly states the importance of self-management at the Scrum team level. Nevertheless, the prevailing cause of many messed-up attempts to use Scrum result from what I call agile micromanagement, a pseudo-commitment to agile principles only to be overridden whenever it seems beneficial from a stakeholder’s or manager’s perspective.

Join me and delve into the importance of self-managing Scrum teams in less than two minutes.

Agile Micromanagement — Making Your Scrum Work #27 —
Continue reading Agile Micromanagement — Seriously? Making Your Scrum Work #27

Why Agile Turns into Micromanagement

TL;DR: Why Agile Turns into Micromanagement

Agile turns into micromanagement as a result of the middle management’s resistance to change. Despite better knowledge, changing an organization into a learning one that embraces experimentation and failure is not in everybody’s best interest. Self-organizing, empowered teams often conflict with the middle management’s drive to execute personal agendas, self-preservation being one of them.

You guessed right: it is time for a rant and short “checklist” to get the discussion going in your organization.

Agile micromanagement: autonomy, mastery and purpose
Continue reading Why Agile Turns into Micromanagement

Agile Management Anti-Patterns — An Introduction for Aspiring Servant Leaders

TL; DR: Agile Management Anti-Patterns

Learn more about agile management anti-patterns the aspiring servant leader should avoid during the organization’s transition: From applying the Stage-Gate® approach through the back door to the ‘where is my report’ attitude to other beloved signs of applied Taylorism.

Agile Management Anti-Patterns: An Introduction for the Aspiring Servant Leader —
Continue reading Agile Management Anti-Patterns — An Introduction for Aspiring Servant Leaders

Agile Failure Patterns in Organizations 2.0

TL;DR: Agile Failure Patterns — Why Agile is Simple and Complex at the Same Time

Agile failure seems to be increasingly more prominent nowadays despite all the efforts undertaken by numerous organization embarking on their journeys to become agile.

The funny thing is: Who would disagree that the four core principles of the Agile Manifesto

  1. Individuals and interactions over processes and tools
  2. Working software over comprehensive documentation
  3. Customer collaboration over contract negotiation
  4. Responding to change over following a plan

— are derived from applying common sense to a challenging problem? Moreover, the application of those principles might be suited to fix numerous organizational dysfunctions and reduce an error-prone and complex social setting to maybe just a complicated one?

Age of Product: Agile Failure Patterns in Organizations
Continue reading Agile Failure Patterns in Organizations 2.0

Why Engineers Despise Agile

TL;DR: Why Engineers Despise Agile

The agile consulting industry repackages an originally human-centered, technology-driven philosophy into a standardized, all-weather project-risk mitigating methodology. Sold to command & control organizations, their middle managers turn “Agile” into a 21. century adoption of Taylorism for knowledge workers. Beyond this meta-level, the reasons, why engineers despise Agile, fall into five categories: Control, manipulation, monitoring, technology and teamwork.

Agile Failure Patterns: Why Engineers Despise Agile

🗞 Shall I notify you about articles like this one? Awesome! You can sign up here for the ‘Food for Agile Thought’ newsletter and join 35,000-plus subscribers.

🎓 Join Stefan in one of his upcoming Professional Scrum training classes!

Continue reading Why Engineers Despise Agile