Why Use SCM

Why Use SCM?

Because...

SCM encompasses the practices and procedures for administering source code, producing software development builds, controlling change, and managing software configurations.

Specifically, SCM ensures the integrity, reliability and reproducibility of developing software products from project start to release.

There are many reasons why teams and individuals use SCM.

However, they can be grouped into these categories:

• Efficiency
• Reproducibility
• Traceability
• Configuration Controls

Developers can focus on writing code that meets their customer requirements.

Too many times, developers are side-tracked with build or configuration problems which distracts them from their primary function, writing solid applications.

The efficiencies gained from an SCM team creating and maintaining the automated software builds and deployment automation greatly frees the developers to do what they do best.

• Software Builds are Standardized, Repeatable and Managed
• Individual Development Teams do not have to Define/Redefine Build Process
• Build Results are Immediately Published to Build Dashboard
• Ensure Rapid Resolution to all Build Issues
• Parallel Builds and Development for Faster Development Iterations
• Configurations are Known and Published
• Fully Automated Installation Procedures
• Encapsulate Run-time Server Configurations
• Reduce Development Cycle

Reproducibility ensures that the output of the software build process produces the same result every time.

It eliminates the guess work

• Repeatable Software Builds
• Confidence that the Build Results are Valid
• Produces Evidence the Build Succeeded
• Creates Repeatable Installation Process

Trace ability ensures that an organization can track a change from source code all the way to installed software product.

• All Source Files are Labeled
• All Build Artifacts are Versioned
• Test Environments are Controlled
• Produce Build and Installation Logs

Controlling Configurations enables organizations to ensure that they know precisely what is in a new build and what changes are being tested.

Controls Include:

• Change Control Processes
• Build of Materials
• Proper Defect Tracking Procedures
• Audit-able Build and Install Logs

The benefits are many, but the overwhelming reason to use SCM on your development projects is...

The increased likely hood of the project succeeding on time and within budget.

Why Use SCM

Software Build Best Practices

Why Use Source Control