Agile Methodology


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 




Source:

http://en.wikipedia.org/wiki/Agile_software_development




Agile - what’s the difference?

• Agile methods are adaptive rather than predictive. 
Engineering methods tend to try to plan out a large 
part of the software process in great detail for a 
long span of time, this works well until things 
change. So their nature is to resist change. 
The agile methods, however, welcome change. 
They try to be processes that adapt and thrive 
on change, even to the point of changing themselves.

• Agile methods are people-oriented rather 
than process-oriented. The goal of engineering 
methods is to define a process that will work 
well whoever happens to be using it. Agile methods 
assert that no process will ever make up the skill 
of the development team, so the role of a process 
is to support the development team in their work.

Martin Fowler, independent software design consultant.