What does it mean to be Agile? There are 3 common answers that I’ve summarised:
- It’s a corporate bullshit.
- Everyone interprets it differently, whatever works for you.
- You’re doing it wrong.
Somewhere between those lines, there’s a subset of people who truly believe that Agile is helping them so much in their daily life. I’m one of them.
I’m afraid I might have over-simplified the common sentiment of Agile in the tech community. However, what I’ve loved so much about this community are the people that have shown me how great Agile can be in the best way possible by bringing me in their journey, seeing the values for myself, and structuring frameworks and environments where I get to explore safely and help build a better culture.
And that’s one of the value in the Agile Manifesto, to value “Individuals and interactions over processes and tools”. We value individuals as human beings and trustworthy. We also value the interactions between individuals more than creating sets of rules or using specific set of tools.
There are many Agile writers out there that would be more comprehensive and most certainly helpful. But I’ve not found many that doesn’t focus on “delivery” or “customers”. As a developer who’s worked in various teams claiming to do Agile for over 5 years, and if you are also a developer, you would agree that most of these articles are irrelevant to us.
I’m not arguing that the customers are not the highest priority, they are. What I’m trying to say is that we’ve done so well in satisfying the customers we sometimes forget about the people behind it.
People are my passion. Human mind intrigues me and it’s my daily amusement to learn about myself, others and the interactions between. In this series, I’d like to explore on how Agile can help me as a developer and make my job less miserable. They’ll be focusing around people and not just developers but from a developer’s point of view. Stay tuned for the next one.