SCMWise.com

SCM War Stories


SCM War Stories are a collection of software engineering anti-patterns that SCM professionals have all experienced.

Hopefully, these stories have long been fixed and never again to be repeated.

To help in that endeavor, we have linked each story to an accompanying software development anti-pattern and best practices.

The end goal is to substantiate a set of SCM Best Practices that can benefit all development teams and organizations.

If you have a war story of your own please send it to us.

We would gladly consider including it if it is in our theme.

Please include your best practice that fixed the problem.


Submit your own SCM War Stories


War Stories Name War Stories Description SCM Best Practice
Circumventing Build Process This happens when people get together and decide that the schedule is more important than software quality. Automated Build Process
Untested Software Normally due to haste or rushing a project or a release out the door before it is ready. Quality Assurance


Software Build Best Practices

Following Software Build Best Practices helps ensure that your development environment is always in a state to build. It also ensures that you are not becoming an SCM War Stories candidate.

For more information about Software Build Best Practices


Source Code Administration Best Practices

  • Build Early and Build Often
  • Fully Automate the Build Process
  • Daily full system builds
  • Continuous Integration builds
  • Creating a repeatable build process
  • Using a secure and dedicated build server
  • Building in a clean workspace
  • Require all necessary files be checked-in prior to the build
  • Label the source code in each build with a unique identifier.
  • Create a BOM, bill of materials, of the source code versions for each build
  • Create a build manifest of the build artifacts.
  • Create and keep your build logs
  • Send build status emails
  • Track release baselines of your software build

For more information about Software Build Best Practices


Software Development Life Cycle Methodologies

There are several different Software Development Life Cycle Methods.

Some have been around for years and years and some are relatively new.

For more information about Software Development Life Cycles Models


Software Development Process

Software Development Processes are standards that a Software Development Team uses to help manage, control and report on their software development.

Here are some very typical SDP Steps:

  • Plan
  • Define
  • Construct
  • Test
  • Deploy

For more information about Software Development Process


Software Engineering Best Practices

There are many Software Engineering Best Practices.

Here are some of the more commonly used SE Best Practices

  • Iteratively Develop Software
  • Actively Manage Specifications and Requirements
  • Develop and Leverage Component-based Software
  • Continuously Review and Improve your Software Development Practices
  • Verify and Quantify Software Quality
  • Manage Software Change

For more information about Software Engineering Best Practices


Software Engineering

The IEEE Computer Society defines Software Engineering as the application of a systematic, disciplined and quantifiable approach to the development, maintenance and operation of software.

For more information about Software Engineering



Software Configuration Management Table of Contents

Software Configuration Management Software Configuration Management are the practices and procedures for administering source code, producing software development builds, controlling change, and managing software configurations.

Software Configuration Management Software Configuration Mgmt is a software development support and control function. Specializing in software building, installation packaging, change control and configuration management.

Software Configuration Management Plan This document will cover source code administration, build environment standards and define the process by which new components will be added to builds, and a common understanding of how we will manage broken builds.

Software Configuration Management Systems Software Configuration Management Systems are the end-to-end tools and procedures that encompass the Software Configuration Management Systems. These are more than just software builds and version control tools. These are the processes you build that surround these tools.

Software Configuration Management Strategies Software Configuration Management Strategies can be difficult to define. Your SCM strategies can be as simple as providing excellent SCM service, but they can be more complex by introducing process improvement to your already existing service.

Software Configuration Management Best Practices Software Configuration Management Best Practices are designed and implemented to ensure software quality, integrity and reproducibility. Best Practices are methods and techniques that are proven to be the most effective way of ensuring repeatability of a processes.

General Best Practices Software Configuration Management Best Practices are designed and implemented to ensure software quality, integrity and reproducibility. Best Practices are methods and techniques that are proven to be the most effective way of ensuring repeatability of a processes.

SCM Plan This SCM Plan is a template model for software applications that require a disaster recovery plan.

SCM Books SCM Books is a collection of books and descriptions that can be a valuable resource and background for installation packaging, software builds, source control, software engineering or engineering in general

Genius Richard Feynman Genius Richard Feynman was written by James Gleick. Genius - The Life and Science of Richard Feynman a 20th century Physics.

Genius James Gleick Genius James Gleick - The Life and Sciences of Richard Feynman.

SCM Performance Goals SCM Performance Goals are set to help the SCM Engineer achieve high performance standards. The goals need to be clear, direct and ongoing feedback from management.

SCM Goals SCM Goals are a sample set of performance objectives that can be used as an example of typical Software Configuration Management Goals.

Forrester Reports This page contains a listing of Forrester Reports for SCM tools. Forrester is a leading company in discovering vendor tool directions and consumer trends. This is a listing of Forrester Reports of SCM tools.

Software Engineering The IEEE Computer Society defines Software Engineering as the application of a systematic, disciplined and quantifiable approach to the development, maintenance and operation of software.

SCM War Stories SCM War Stories are a collection of typical SCM anti-patterns that most experienced SCM Engineers have all lived through.

Circumventing Build Process Circumventing Build Process happens for many reasons. For example, it can happen because someone decides schedule is more important than software quality. Another example, might be that the person making the decision to circumvent the build process does not understand the implications of their decision.

Untested Software Untested software is an anti pattern due to a project that is behind schedule. A decision to proceed with the delivery to demonstrate progress of a project over the proper testing has taken place to ensure quality. Untested Software is a common Software Engineering Antipattern.

What is SCM What is SCM? SCM encapsulates 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 planning to release.

Why Use SCM Why Use SCM? Software Configuration Management ensures software build repeatability and reproducibility. SCM enforces Source Code Administration Best Practices and proper Software Change Management practices are followed.

SCM Websites Software Configuration Management Websites a listing of top SCM sites and other interesting Websites. This page attempts to identify the truly unique Websites. Please visit them.

SCMWise Software Configuration Management SCMWise is dedicated to SCM. This site is a central repository for the collection of best practices, processes, methodologies and tools that surround SCM.




SCMWise Configuration Spec



© Copyright 2007 - 2016
Powered by Site Build It!
Page copy protected against web site content infringement by Copyscape SCMWise.com's Privacy Policy
ADD TO YOUR SOCIAL BOOKMARKS: add to BlinkBlink add to Del.icio.usDel.icio.us add to DiggDigg
add to FurlFurl add to GoogleGoogle add to SimpySimpy add to SpurlSpurl Bookmark at TechnoratiTechnorati add to YahooY! MyWeb