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.

DAY 3 …This one is pretty self explanatory: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. We like to deliver frequently in short bursts, and this enables many good things.

DAY 2 ... Anticipate and account for change. Expect change. Because you don't want to deliver the wrong thing just because you planned it. The plan is just that, a plan. 'The map is not the territory'.

Day 1 .. and the first of the series! Kicking off with… our highest priority is to satisfy the customer through early & continuous delivery of valuable software