In
software development
Software development is the process of conceiving, specifying, designing, programming, documenting, testing, and bug fixing involved in creating and maintaining applications, frameworks, or other software components. Software development invol ...
, projects and programs, a change control board (CCB) is a committee that consists of Subject Matter Experts (''SME'', e.g. software engineers, testing experts, etc.) and Managers (e.g. Quality Assurance managers), who decide whether to implement proposed changes to a project. The main objective of a CCB is to ensure the client accepts the project. Factors affecting a CCB's decision can include the project's phase of development, budget, schedule, and quality goals.
Change control (see
Scope management) is also part of
Requirements engineering
Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering.
The first use of the term ''requirement ...
. CCBs are most associated with the
waterfall method
The waterfall model is a breakdown of project activities into linear sequential phases, meaning they are passed down onto each other, where each phase depends on the deliverables of the previous one and corresponds to a specialization of tasks. ...
of software development, but can be seen as having analogues in some implementations of
Agile software development
In software development, agile (sometimes written Agile) practices include requirements discovery and solutions improvement through the collaborative effort of self-organizing and cross-functional teams with their customer(s)/ end user(s), ad ...
.
The Change Control Board will review any proposed changes from the original
baseline requirements that were agreed upon with the client. If any change is agreed upon by the committee, the change is communicated to the project team and the client, and the requirement is baselined with the change. The authority of the Change Control Board may vary from project to project (see e.g.
Consensus-based decision making
Consensus decision-making or consensus process (often abbreviated to ''consensus'') are group decision-making processes in which participants develop and decide on proposals with the aim, or requirement, of acceptance by all. The focus on es ...
), but decisions reached by the Change Control Board are often accepted as final and binding.
A typical Change Control Board might consist of the development manager, the test lead, and a product manager. Less commonly, the client might directly advocate their interests as part of the Change Control Board.
Change Management - Change Management Process
/ref>
See also
* Change management (ITSM)
* Change-advisory board A change-advisory board (CAB) delivers support to a change-management team by advising on requested changes, assisting in the assessment and prioritization of changes. This body is generally made up of IT and Business representatives that include: ...
* Project management
Project management is the process of leading the work of a team to achieve all project goals within the given constraints. This information is usually described in project documentation, created at the beginning of the development process. Th ...
* Requirements engineering
Requirements engineering (RE) is the process of defining, documenting, and maintaining requirements in the engineering design process. It is a common role in systems engineering and software engineering.
The first use of the term ''requirement ...
* Configuration management
Configuration management (CM) is a process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its life. The CM proc ...
References
Software development process
{{Soft-eng-stub