configuration management

Wanted: A software configuration management (SCM) tool that (a) provides the capabilities necessary to support an organization's software development process, (b) integrates seamlessly with the Integrated Development Environments (IDEs), (c) facilitates the organization's change management process, (d) facilitates the organization's build process, (e) requires only modest training for technical staff , and (f) encourages proper and effective use by technical staff.

The best way to make a project succeed is to communicate effectively. When all levels of the project share the goals, vision, constraints, and plan, everyone on the team can pull as hard and as creatively as possible in the right direction. Failing to share the goals and vision underlying a software configuration management (SCM) implementation can cause it to fail.

There is a good amount of training, discussion and many articles concerning software configuration management (SCM) standards that tell us to implement configuration identification, status accounting, routine auditing, etc. All of this information is good and very important because it helps us understand the overall objectives. Rarely, though, do you find real tangible approaches for "how" to actually implement solutions that accomplish the objectives. This article will discuss a typical SCM Implementation engagement focusing on some practical best practices in order to achieve the objectives of the many CM standards out there. These best practices won't apply to all situations.

Patterns and pattern languages are tools that can be used to help a team be more effective and agile. They can lead to robust, effective solutions, because the solutions that patterns can lead you to take the environment into account. They also solve problems in a way that makes the system work better. This article will show you how you can use existing patterns to improve your SCM process. It will also help you to understand where existing patterns and pattern languages have gaps.