Content area
Full text
In the IT industry, everyone has witnessed the continued increase of Agile (with a capital A) adoption over the past 16 years since the Agile Manifesto was written. Everyone who has led an organization under Agile has discovered that Agile is easy to understand but hard to master. Delivering Agile takes hard work.
What can we learn from comparing Agile versus agile? That question came up recently in my delivery oversight, especially when it came to identifying Agile anti-patterns. That is, those behaviors and ceremonies that go in direct contrast with good Agile practices.
When teams are delivering poorly, it does not matter if they are following scrum, traditional waterfall, Kanban or no set process at all. Teams have been failing at IT delivery ever since IT delivery existed.
What matters is having experience at identifying the signs of poor delivery and then having even more experience at creating effective solutions with the team. The more advanced step is to have the team solve problems themselves in a self-organizing fashion and support them when they encounter any challenges.
What is the opposite of agile? Here are the antonyms for the word agile from Word Hippo:
Clumsy, apathetic, depressed, dispirited, down, dull, ignorant, inactive, lazy, lethargic, lifeless,...