Agile Is Just a Hammer: Reflections on Misusing Agile Practices

In 2014 two "hammers" were popular, and the author likens the current craze for agile practices to another hammer that many wield without understanding.

More and more people around you are talking about agile, gathering to discuss it, and the author asks whether you have been "hit" by this trend.

Conversation A asks whether teams split user stories and how they estimate; B replies they use card‑based estimation, suggesting a superficial adoption of agile techniques.

Another dialogue shows a team claiming to practice TDD enthusiastically, yet admitting they cannot sustain it, while a third participant silently doubts their own use of TDD.

Pair programming is discussed: some teams have paired, receiving managerial support, while others face resistance from managers who view it as a waste of manpower.

Teams talk about adopting Kanban and Scrum, praising the visual impact and stakeholder attention that boards provide, and encouraging others to try pilot projects.

The conversation shifts to scaling agile with SAFe, noting its hype in North America, large‑scale adoption, and the pressure on managers to bring in consultants to implement it.

Later, participants mention a buzzword "instance demand" (or similar), expressing confusion about its purpose and why they should adopt it, simply because it is fashionable.

Finally, the topic of continuous delivery arises; some teams say they cannot adopt it due to quarterly release cycles in banking or telecom, while others lament managerial pressure to enable on‑demand releases despite operational constraints.

The article concludes with the classic saying, "If the only tool you have is a hammer, you tend to see every problem as a nail," applying it to agile: treating agile as a single hammer leads to misapplication, and practitioners should question why they use specific practices and whether they truly fit their context.