I think I have taken away quite a lot from my study on Agile. Though it is not suited to all projects I can see some projects really benefiting from its practices.After having written on most of the topics I looked at I thought I’d provide a summation.

Design: Is emergent

Testing: Cannot be built into a product. It should be part of the product.

Refactoring: Shouldn’t change existing functionality. It should enhance existing functionality.

Testing: Development is the customer of testing. Not the other way around.

Time boxing: Shows you how efficient you are or aren’t.

Decisions: Trying to decide too much early on is often worse then deciding too little.You more effort you put into something the less likely you are to throw it away when the time comes.

Documentation: Form is, (to an extent) more important than content. Pic blogs, wikis, user stories, code intentions whilst each simplistic in nature convey more than a 200 page document built to NASA specifications.

Work: Work gets done when people want to do it.

Risk: Spiking risk/technology/knowledge/skill gaps doesn’t increase the chance your project will succeed. It decreases the chance your project will fail.It’s been interesting looking at a model unlike other models I’ve encountered. Whilst you many not be able to apply all of agile’s teachings to a project there are undoubtedly some that can be implemented as no-brainers.