Have We Taken Agile Too Far?

In the 90s my team used various XP practices: daily standups, TDD, Pair Programming, timeboxing, etc. But we stopped short of calling this collection of practices a "methodology".

Then the Agile guys wrote a manifesto.

For several years it was great, the manifesto was a great place to start a conversation with management or skeptical developers.

I've seen Scrum implemented well and Scrum implemented poorly. And there are other methodologies our there: crystal, lean, Kanban, etc.

I think the authors of this piece are onto some form of organizational anti-pattern: an over-reliance on tools rather than common sense, ignoring planning when you really should be planning, ceremonies when they're of no use for your team, etc.

If you think your team is doing Agile wrong, maybe show some people this article to start a conversation.