
A Practical Approach for Selecting and Adopting an SCM Tool
Address
Michael Sayko mss@acm.org
Michael Sayko – December 2003
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) and other development tools used by the organization, (c) facilitates the organization’s change management process, (d) facilitates the organization’s build process, (e) requires only modest training for technical staff before it can be installed and adopted, and (f) encourages proper and effective use by technical staff. Does this request sound like a delusion? It need not be a fantasy with proper planning and adequate organizational support. Below is a practical approach I used to help an organization select and adopt an SCM tool.
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) and other development tools used by the organization, (c) facilitates the organization’s change management process, (d) facilitates the organization’s build process, (e) requires only modest training for technical staff before it can be installed and adopted, and (f) encourages proper and effective use by technical staff. Does this request sound like a delusion? It need not be a fantasy with proper planning and adequate organizational support. Below is a practical approach I used to help an organization select and adopt an SCM tool.
Reviews (0)
Be the first to review this listing!
