SCM & the Agile Manifesto

This page describes how we see the values of the Agile Manifesto relate to software configuration management (SCM).

Individuals and Interactions over Processes and Tools.

SCM processes and tools should support the way that you work, not the other way around. Often, the reason behind frustrating SCM processes is trying to impose an overly-rigid process on a team, or attempting to use a tool that imposes a process into an organization that is different than the process the organization needs.

Working Software over Comprehensive Documentation.

SCM can automate development policies and processes with executable knowledge rather than have the team rely on documented knowledge. You can make things easy for developers and ensure that necessary procedures are followed by writing scripts instead of documenting procedures.

Customer Collaboration over Contract Negotiation.

SCM can facilitate communication and interaction among stakeholders and help manage expectations. The appropriate tools and processes can provide customers with visibility into the status of a project and allow them to contribute to the project where appropriate.

Responding to Change over Following a Plan.

SCM is about facilitating change, not preventing it. Use SCM policies and structures that allow your development team to progress at an appropriately rapid pace. Don't make the entire team move at the pace of the slowest changing component.