Years ago while working at a young start up it dawned on me, like hundreds others, that I needed a name for our particular brand of agile software development. Ours was a different style, unique, personal, successful – not like all the others, right? But I wanted it to last because I loved it. I wanted it to last forever, but it didn’t. And since then I have always tried to replicate that success to varying degrees of success. Here are some of the key aspects:
- Where Agile focuses on the need to move quickly and change easily, Nimbile emphasizes the ability to do such, but not necessary the need to. Point being: too frequent or unnecessary change is unhelpful at best and at worst crippling.
- Positive, fun and productive work environment. Yes all those things are necessary. I do not believe that the ends justify the means, I believe that the end, however cast is a product of the means and carries with it the essence of those who made it.
- Believe that what you are doing is good for your customers, the company, the employees and in any small degree, the world.
- Do the right thing at the right time. Don’t wait to change when you need to and stick to what is working.
- Dream, test, measure, execute. Then repeat. If you didn’t know what you were doing and if you don’t know that it’s working then you’re just wandering. That’s nice, but I need to run a business here.
- Almost everything else good that is Agile and nothing of the bad of all the other methods(tm). That’s right. That makes this an airtight claim to being _the best_ methodology ever!
I want to take time to flush this out more, and in particular share experiences from each of the subsequent companies that I’ve worked for. Hopefully this will allow me to refine the definition of Nimbile and show how it works and what you need to make it work.