Document Controls

  • View a Print Friendly version of this document

    Print
  • Toggle highlighting of search terms in this document

  • Text Size: 

    • A (normal)
    • A (larger)
    • A (largest)

For Application Development & Delivery Professionals

Primary Analyst Photo Document Information Rate this Document

October 19, 2007

Standardized Software Change And Configuration Management: Achievable Goal Or Wishful Thinking?

by Jeffrey S. Hammond

with Carey Schwaber, Catherine Salzinger

Average:
(2 ratings)

This is an excerpt

Executive Summary

The merits of integrating software change and configuration management (SCCM) are well established. But for many shops, standardizing on a single SCCM solution is more an ideal than a reality. These shops use multiple software configuration management (SCM) tools for different projects, platforms, and technologies, and near-term consolidation simply isn't feasible. Instead of trying to standardize on a single, unified SCCM solution, some of these shops are integrating multiple SCM tools with a single change management tool. This heterogeneous SCM strategy lets them enforce a common process and collect apples-to-apples metrics while permitting developers to use the SCM tool of their choice.

This is an excerpt

Buy Risk-Free

Price: US $499

Our Service Guarantee: If you are not completely satisfied with this document, notify Forrester within 24 hours of purchase for a full refund.

Already a Forrester Client?
Log in to read this document.

Add to cart

Save and Share

Document Tools

Spread the word: