|
|
|
Home >
Best practices >
Change control management
|
Change Control Management |
| Change Control is a formal process used to ensure that changes to a
product or system are introduced in a controlled and coordinated manner.
It reduces the possibility that unnecessary changes will be introduced to
a system without forethought, introducing faults into the system or undoing
changes made by other users of software. |
| On moderate to very large projects, a central control mechanism is needed
to ensure that every change is properly considered and coordinated. That's why
on such projects, FlexOrbits establish a Change Control Board. It includes the
members from
design,
development, and test teams.
It also sometimes includes the members from the customer team. Its purpose is to
ensure that all concerned parties properly consider every baseline change and
that every change is authorized before implementation. The Change Control Board
(CCB) is the body that reviews all major change requests, approves them, disapproves
them, or defers them for more information. The Change Control Board produces its
rapid-development
benefit by raising the visibility of feature creep and reducing the number of uncontrolled
changes to the product. |
|
|
