Agile SCM

Agile SCM - We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Implementing an adaptive SCM process is no different than implementing an adaptive development process.

Wisely implemented SCM patterns provide the following benefits.

The Agile Manifesto

• Reproducible software builds and build artifacts
• Environment consistency and integrity
• Proper coordination and hand-offs between the development and test teams

Unwisely implemented Software Configuration Management patterns lead to

• Process for process-sake development practices
• Development bottlenecks and slowdowns
• Frustrated development teams

Teams can implement A.G.I.L.E SCM by following the above stated values.

• Be quick to adjust designs and processes to better meet the customer's expectations
• Avoid over engineering of processes and documentation

Goal Driven

• Keep the customer priority as your number one priority
• Focus on delivering the highest business value to the customer

It might mean process modification as opposed to document or risk adverse driven.

Lean

• Streamline processes
• Eliminate redundancies
• Intuitive design
• Eliminate excessive documentation. Only document what is truly helpful

Emergent Behavior

• Short development cycles
• Frequent releases

Sources

• Brad Appleton - I read so much of Brad's material it would be impossible to accurately give him specific credit.
• A.G.I.L.E Manifesto