The
configuration management practice helps teams to:
·
Identify
and document the functional and physical characteristics of configuration items.
·
Define
which persons or teams are authorized to manage configuration items.
·
Establishing
procedures for handling changes to configuration items. These procedures define how change can be managed, tracked and
controlled.
·
Documenting and
reporting information needed to manage configuration items effectively, including the status of configuration items
which are subjected to change.
·
Perform
configuration
audit to verify integrity of baselines and releases.
Relationship
to other practices
This
practice is related to many other useful practices. For example:
-
Formal
Change Management - An explicit approach for controlling changes, including defining states for the change
request artifact and tasks for transitioning the change request artifact between states
-
Iterative
Development - The iterative approach is the single most significant improvement to the way we build software
products in decades, and has significantly improved project success because the feedback cycle is built into
the software development lifecycle.
-
Risk-Value Lifecycle - The risk-value lifecycle practice supplements the iterative development and
release planning practices with the unified process lifecycle. This lifecycle identifies four phases, each of
which attempts to balance value provided against risk mitigation appropriate to the
phase.
-
Continuous Integration - In a Continuous Integration practice, team
members integrate their work frequently (at least daily).
-
Stage Integration - This practice covers the integration of small subsystems into progressively larger ones
until the whole system is integrated.
|