This article looks at satisfying the principles of Configuration Management with varying degrees of tool support, which we classify from Version Control at one end, to true CM tools (and beyond!). Many agile developers restrict themselves to tools that are more on the version control end, so we aim to highlight the differences, and particularly point out certain features which can make your life a lot easier.

What is agile CM? If you think it's doing the minimal amount of CM, think again. Instead, it's minimizing and streamlining the work to do all of the CM tasks that are necessary. It adapts to changing CM requirements fairly easily. Agile CM doesn't just happen - it's a combination of good CM process, good CM tools, and CM automation. If you fall short on any of these, your CM process will not be very agile.

Agile methods for software development are one of the hottest movements in the methodology field. Agile methods provide a means of adapting quickly for teams facing unpredictable or rapidly changing requirements. Agile introduces a structured approach to software development (more structured than most "bandwagon" enthusiasts realize).

The traditional approach to managing productivity is that employees punch a clock – in at 8, out at 5 – and employers must assume work is being done during the intervening hours.  However, the current reality for many, if not most, businesses, is that the traditional approach no longer works.  It has become unclear whether or not work is being accomplished regardless of hours logged at the office.  With the increase in outsourced and offshore teams, many developers are scattered across different states or even different continents and throughout a variety of time zones.  As a result, it’s not possible for a manager to ‘swing by’ a developer’s cube to get a status update on a project or even just to do a quick check that a team member is present and productive.