IVI Framework Viewer

Configuration Management

C3

Manage the software, application, platform, and service component configurations and inter-relationships.

Improvement Planning

Practices-Outcomes-Metrics (POM)

Representative POMs are described for Configuration Management at each level of maturity.

2Basic
  • Practice
    Ensure that there is a manual configuration manager in place, and maintain inventories of the versions of components and applications used in solutions.
    Outcome
    Teams may have minimal interaction with the configuration manager or inventory of component versions.
    Metrics
    • # of hours configuration manager spends on generating solutions.
    • # of failed deployments due to poor configuration management.
    • # of hours spent on configuration management per release.
  • Practice
    Put in place a configuration management tool.
    Outcomes
    • While there may be a configuration management tool in place, it might not be consistently used.
    • It might also not be integrated with other tools in the toolchain.
    Metric
    Existence of configuration management tool.
3Intermediate
  • Practices
    • Ensure that the configuration manager application applies clear configuration controls that are used consistently to maintain a record of solution configurations and baselines.
    • Ensure that versioning, branching, and a source control strategy are well-defined.
    Outcome
    Any version of a solution can be generated at any time.
    Metrics
    • # of hours configuration manager spends on generating solutions.
    • # of failed deployments due to poor configuration management.
    • # of hours spent on configuration management per release.
  • Practices
    • Ensure that there is a consistent approach to configuration management across geographical sites.
    • Integrate the configuration management tool into the toolchain.
    Outcome
    Identical solutions can be generated in multiple geographic locations.
    Metric
    % of geographical sites with a consistent approach.
4Advanced
  • Practices
    • Ensure that configuration management is a standard practice and central to the deployment, release, and operation of solutions.
    • Ensure that multiple instances can use different test configurations, with test configurations source controlled and built into the application.
    Outcome
    Any version of a solution can be generated quickly and easily at any time.
    Metrics
    • # of hours configuration manager spends on generating solutions.
    • # of failed deployments due to poor configuration management.
    • # of hours spent on configuration management per release.
  • Practice
    Ensure that configuration controls are implemented consistently and automated to preserve integrity.
    Outcome
    Identical solutions can be generated in multiple geographic locations, with some automation.
    Metric
    % of configuration control automation.
5Optimized
  • Practices
    • Ensure that configuration management is flexible and reactive and can support rapid recreation of specific configurations, including leveraging configurations available from the cloud ecosystem.
    • Ensure that configuration management can support a broad range of solutions and team structures.
    Outcome
    Any version of a solution can be generated at any time quickly, easily, and automatically.
    Metrics
    • # of hours configuration manager spends on generating solutions.
    • # of failed deployments due to poor configuration management.
    • # of hours spent on configuration management per release.
  • Practice
    Ensure that configuration management tools are fully automated and interoperable across the entire ecosystem.
    Outcome
    Identical solutions can be generated in multiple geographic locations, and be fully automated.
    Metric
    % of configuration control automation.