I wasn’t really sleeping but otherwise engaged. I was focused on the software development using Microsoft tools; old and new. I spent most of the time in looking into how a project can be brought to more close to the quality processes, and on continuous improvement on delivery. So, when a sound from the rugby field hit me right at my workplace, I, frankly speaking, shrugged it off. After all, borrowing murky words from a different area is an old practice to draw attention within the software community; the list is practically endless.
With the time, I started hearing it again and again. Our classical concept of waterfall model has got faded quite some time back. The iterative approach of software development came into practice and has been thriving a lot. Although the commonly accepted process guidelines like CMMI standards don’t exactly specify what methodology to follow, many of its processes work better with iterative model.
On the side, the attempt to find out something different went on. Started with Extreme Programming, it started to take shape into more explicit and recognizable form. The name Agile Programming probably came much later with some solid implementation successes. And with success, the noise level amplified. Finally, the day had come when I have started to follow the Agile Programming; the days to scream in a Scrum.
In this series of Agile Intelligence, I will blog my learning on Agile Programming so far, and to see how our own delivery processes can fit with it. While, I am not too sure how frequent I will be in writing this, but I will certainly look for your comments on Agile Programming as I blog forward.
Meanwhile, I must recommend you go through the website of Agile Alliance. It’s a good one to start with.
