Page 254 - DCAP304_DCAP515_SOFTWARE_PROJECT_MANAGEMENT

Software Project Management

Notes when a document or a piece of code is first written, or an agile team working in close contact
with users and sponsors, if work can be performed in an informal way without bureaucracy and
heaps of paper. It may also—and will typically, for most important configuration items—
consist of a number of people, such as the project manager, a customer representative, and the
person responsible for quality assurance.
Process Descriptions

The methods, conventions, and procedures necessary for carrying out the activities in change
control may be;
 description of the change control process structure,
 procedures in the life cycles of events and changes,

 convention(s) for forming different types of configuration control boards,
 definition of responsibility for each type of configuration control board,
 template(s) for event registration,
 template(s) for change request.

Connection with Other Activities

Change control is clearly delimited from other activities in configuration management, though
all activities may be implemented in the same tool in an automated system. Whether change
control is considered a configuration management activity may differ from company to company.
Certainly it is tightly coupled with project management, product management, and quality
assurance, and in some cases is considered part of quality assurance or test activities. Still, when
defining and distributing responsibilities, it’s important to keep the boundaries clear, so change
control is part of configuration management and nothing else.

Example: Figure 12.6 shows an example of a process diagram for change control. A
number of processes are depicted in the diagram as boxes with input and output sections (e.g.,
“Evaluation of event registration”). All these processes must be defined and, preferably, described.
Figure 12.6: Change Control Process Diagram

248 LOVELY PROFESSIONAL UNIVERSITY