Difference between revisions of "Change control"
(Created page with "Change controlis controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made. ==Defini...") |
(→Definitions) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Change control]]is controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made. | + | [[Change control]] is controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made. |
==Definitions== | ==Definitions== | ||
According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | According to the [[BABOK Guide|BABOK Guide (3rd edition)]], | ||
:[[Change control]]. Controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made. | :[[Change control]]. Controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made. | ||
| + | |||
| + | ==Practice== | ||
| + | :''Main wikipage: [[Change control practice]]'' | ||
[[Category: Business Analysis]][[Category: Articles]] | [[Category: Business Analysis]][[Category: Articles]] | ||
Latest revision as of 03:34, 29 December 2020
Change control is controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made.
Definitions
According to the BABOK Guide (3rd edition),
- Change control. Controlling changes to requirements and designs so that the impact of requested changes is understood and agreed-to before the changes are made.
Practice
- Main wikipage: Change control practice
