DAY 12… and the final post in the series. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly. Did I hear someone say Retrospective?

DAY 11…The best architectures, requirements, and designs emerge from self-organizing teams. Whoa, that’s a bit radical isn’t it? What are we saying here? That we don’t need managers?!

DAY 10… I’ll try and keep things real simple. Simplicity--the art of maximizing the amount of work not done--is essential. We can illustrate this quite easily when you observe agile ways of working.

DAY 9… Continuous attention to technical excellence and good design enhances agility. Strap in it’s going to get technical. In essence paying attention to technical design and refactoring allows the code base to maintain some functional integrity and at the same time expand for the next set of technical functionality, or features, required to meet a customer need.

DAY 8… Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

DAY 7… Working software is the primary measure of progress. This slightly problematically worded principle only refers to software and very much a technology driven view of the world, we’ve evolved to know a lot more than we did in 2001.

Day 6… The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

DAY 5… Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

DAY 4… Where we get friendly. Business people and developers must work together daily throughout the project.