I’ve been learning about Agile, and employing its principles and practices, for a while now.
I was introduced to some of the tenets of eXtreme Programming (XP) in 2000 by a co-worker at a software development company. I liked what I saw, but didn’t get a chance to apply it much at the time. My next opportunity came in 2005, when I got involved in another software development effort that started out in the traditional “waterfall” fashion with a good-sized design document, but changed over to an Agile approach because we all knew that the requirements for the product being built were going to be changing constantly.
My personal discovery of Agile principles and practices renewed my interest in software development (in which I had been involved since 1977). Agile held a promise that I could actually be part of creating some fairly large software systems without them becoming inflexible and unmanageable with growth.
As I learned more, I began to realize something that many others almost certainly know: This Agile stuff has much broader application than just in the world of software. So I adopted a broader viewpoint, and began thinking in terms applying Agile principles and practices to productivity in general.
I’m a big fan of Eliyahu Goldratt’s Theory of Constraints, and find myself reading and re-reading his body of work. I like Goldratt’s clear and concise definition of productivity, and use it myself in practically everything I do work-wise.
Eventually I began training and coaching other people in Agile principles and practices, and developing hands-on exercises that help get the basic ideas across. I’m still doing that today, and intend to keep on doing it, hoping to reach larger and larger audiences.
I’m also hoping that this blog will serve to promote the exchange of ideas between myself an other enthusiasts out there. Please feel free to join the conversation.