Agile Programming

Though there have been different flavours of Agile prior to 2001 ..Its has been gaining widespread popularity these days. I did work in one of the flavours called XP(eXtreme Programming) in 2003.There are similarities and differences But here are my thoughts on the Agile Manifesto!

"We are uncovering better ways of developing
software by doing it and helping others do it.
Through this work we have come to value:

Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan


That is, while there is value in the items on
the right, we value the items on the left more"

The above is from http://agilemanifesto.org/

I do appreciate all the thought process/experiences that went about to create the manifesto.

Who creates processes and tools? isn't it Individuals with interactions?
Working software can be documented,User guides/User training etc are the need for the day as its important to know for whom the software is developed.
Customer collaboration is good for business in general but winning and executing a contract is more important than just mere collaboration...Collaboration needs to speak in terms of revenue.
How can the project plan be created in such a way that it would cater to responding to a change?if you fail to plan your planning to fail.

Both RHS and LHS is equally important.You cannot do without the either.Now the question is what is being valued on the LHS vs RHS is more important.

Do consider checking out the Addendum's to the manifesto...and do add your own based on your experience!Also before Agiling consider what is important to you especially if you are the project manager