Agile

I just wanted to say "Happy Labour Day" to my readers in Canada/ U.S. I hope you are enjoyed a day off. This post is my first post on series of posts on Agile methodology. I don’t want to load my reader with all information at one shot, that’s why I’m breaking Agile methodology into chain of series. I think this methodology is quite new and we have to give some time to this methodology to mature. Furthermore no methodology can’t mature with in it 2-3 years, so Agile methodology also need some more time to mature and IT industries also need more time to alliance with Agile. They also need more time to adjust with this new methodology.

So just for curiosity, I want to know first, what the word Agile means. So according to thefreedictionary.com and link: www.thefreedictionary.com/agile

Def: ag·ile (jl, -l)
adj.
1. Characterized by quickness, lightness, and ease of movement; nimble.
2. Mentally quick or alert: an agile mind.
[French, from Latin agilis, from agere, to drive, do; see ag- in Indo-European roots.]

It’s an adjective with meaning quick in movement, lightness.

Defining Agile in Software development:
An iterative and incremental (evolutionary) approach performed with project stakeholders in a highly collaborative and self organizing manner with just the right amount of ceremony to produce high quality software and timely manner that meets stakeholders changing needs. For more information click on IBM website on agile, link: www.ibm.com/software/rational/agile/resources/