Page 251 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Unit 12: Monitoring & Control

Notes

Notes However, other parameters, such as Scope, Quality, Team Morale, may be used.
Reviews may include the client, Product Owner, other Project Managers or ScrumMasters.

12.4 Change Control

When developing and maintaining a product, changes are inevitable. People make mistakes,
customers need changes, and the environment in which the product operates evolves. In addition,
people constantly develop their knowledge of the problem and their ability to solve it. In
software development, it’s generally said that the solution of a problem will create new problems.
In other words, we get wiser all the time.
The purpose of change control is to be fully in control of all change requests for a product and of
all implemented changes. For any configuration item, it must be possible to identify changes in
it relative to its predecessor. Any change should be traceable to the item where the change was
implemented. Figure 12.5 shows how change control affects and is affected by its environment.
Figure 12.5: Change Control in Context

Inputs

Change control is initiated by an event. An event may also be called a wish for modification but
need not be expressed as a clearly formulated wish. In this context, an event is any observation
of something surprising, unexpected, inconvenient, or directly wrong during usage of the
configuration item. It may, for instance, be:
 A wrong formulation, caught during the review of a document.
 A coding mistake found during a walk-through of a piece of source code.

LOVELY PROFESSIONAL UNIVERSITY 245