TL; DR: My Top Ten Worst Scrum Anti-Patterns
I recently was invited to a Scrum.org Webinar, and I picked a topic close to my heart: the worst Scrum anti-patterns. So, without further delay, here are my top ten of the meanest, baddest Scrum anti-patterns I have experienced.
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.
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.
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 —
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- 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?
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.
Do you want to get this article in your inbox? You can sign up here and join 24k other subscribers