Agile as a term in software engineering derives its meaning from the Agile Manifesto. The Manifesto makes four simple points listed below.
‘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.’
Or, a slightly longer version:
- Process is important, but not as important as people working in effective teams.
- Documentation needs to be appropriate and it needs to make the delivery of working software more efficient, because working software is what is important.
- If you have to rely on a legal contract, the relationship has probably already failed, so put a lot of effort into working with the customer as a partner.
- Things change, people change their minds: deal with it, rather than getting hung up on a plan that is imperfect
This is just a way of turning the original points around to give them added emphasis. It helps me to gain greater clarity anyway 