Addressing Problems, Caused by AMMs
Explore the challenges and solutions of Agile Maturity Metrics in organizations.
Oct 15, 2017
•
3 min read
-
Advanced
Complex Systems
Managing Complexity
Process Improvement
Systems Modeling
Systems Theory
Summary
Agile Maturity Metrics (AMM) are widely used to measure agility improvements at various levels in organizations. However, they differ from Agile Check-Lists, leading to potential challenges like system gaming, conditional attribute weighting, and non-linear attribute correlation. This article advises treating agile attributes as system variables with upstream and downstream relationships to avoid these issues. Learn how to effectively apply AMMs and avoid common pitfalls.
Takeaways
- Agile Maturity Metrics (AMM) are distinct from Agile Check-Lists and should be used carefully.
- Attributes in AMMs should be treated as system variables with complex interdependencies.
- Focus on upstream variables to address systemic issues effectively.
- Organizations should tailor the importance of attributes to their unique context.
- System gaming can occur if AMMs are tied to incentives, leading to manipulation.
Suggested Resources
Change is more like adding milk to coffee
-
Intermediate
3 basic (priorization) assumptions
-
Intermediate
The Day We Stopped Sprinting
-
Intermediate
The Development Team
-
Intermediate