Some of you may have read my personal Agile Adoption Story and possibly thought that it was a good story on Agile Adoption and how Agile can sometime succeed on the first try. I know I’ve read many stories about the pain and suffering on the first Agile projects people have been on.
If you missed the Blog Post on my personal Agile Adoption story, you can find it here:
So given that my first Agile project was successful? What was my #1 Agile Failure? Simply put, it was the fact that my first Agile Project was successful!
Please let me explain. We came out of that first project with a false sense of security. We thought we nailed this ‘Agile’ thing. I mean we didn’t do many of the core Agile practices and still we delivered on time, on budget, and satisfied the client. This false sense of security was at a personal, project, and perhaps even a company level. We thought that we could deliver again with different teams, different problems, and different technologies.
I often say that I would have rather failed slightly on the first project so we knew we still had a way to go. Unfortunately that didn’t happen.
Why did we succeed then?
I believed we succeeded primarily due to the expertise of the development team and the expertise of our client/Product Owner. Having these two factors can address shortcomings in many other areas.
To recap, here are the Agile Practices we did not follow:
- Test Automation
- Continuous Integration
- Kan Ban
- User Stories
- Planning Poker
- Pair Programming
- User Story Mapping
- Paper Prototyping
- User Design Studio
- And many others