The most popular and comprehensive Open Source ECM platform
Let us know more
Software: When Agile Methodology Goes Wrong
A recent article by Karin Ahlbäck, engagement manager at McKinsey, was titled “The Drawbacks of Agility.” The article doesn’t really uncover problems with agility per se. Instead it notes that when agility is “misused” or not correctly implemented, “it can trigger disruption and productivity loss.”
Some things that Ahlbäck notes that might go wrong when businesses attempt to use agile methodology include:
- Cookie cutting. Trying to copy or emulate an agile process implemented elsewhere or which was used on a different project often doesn’t work, especially when applied without a clear understanding of agile.
- Partial implementation. Failure to use agile across all the moving parts within a process won’t achieve full benefits of the approach.
- Failure to measure. Agile, like anything else, can be improved by applying metrics and identifying what’s working and what isn’t. Just because an attempt at agile is implemented doesn’t mean that tuning of the approach isn’t possible.
- Features over quality. Again, another issue not really with agile but with setting priorities. To achieve quality, it’s important to not under prioritize rework and optimization tasks in favor of new features and development, otherwise quality will suffer.
The article concludes that agile is “not a silver bullet. The most successful agile adopters employ a well-aligned, situation-specific strategy that weighs the investment against expected benefits.”
0 comments on “Software: When Agile Methodology Goes Wrong”
1 Pings/Trackbacks for "Software: When Agile Methodology Goes Wrong"
-
[…] Software: When Agile Methodology Goes Wrong Formtek Blog (blog) […]