Purpose:
<?>
Objective:
Changes to the work products under configuration management are tracked and controlled.
Description:
<?>
Inputs:
<?>
Outputs:
<?>
Controls:
<?>
Task/User Story and Task Instructions:
Track Change Requests
- Using the <?>, [the ?] with support from <?> is responsible for initiating and recording change requests in the change request database.
- Using the <?>, [the ?] with support from <?> is responsible for analyzing the impact of changes and fixes proposed in change requests.
- Using the <?>, [the ?] with support from <?> is responsible for categorizing and prioritizing change requests.
- Using the <?>, [the ?] with support from <?> is responsible for reviewing change requests to be addressed in the next baseline with
relevant stakeholders and getting their agreement. - Using the <?>, [the ?] with support from <?> is responsible for tracking the status of change requests to closure.
Control Configuration Items
- Using the <?>, [the ?] with support from <?> is responsible for control changes to configuration items throughout the life of the product or service.
- Using the <?>, [the ?] with support from <?> is responsible for obtaining appropriate authorization before changing configuration items are entered into the configuration management system.
- Using the <?>, [the ?] with support from <?> is responsible for checking in and checking out configuration items in the configuration management system for incorporation of changes in a manner that maintains the correctness and integrity of configuration items.
- Using the <?>, [the ?] with support from <?> is responsible for performing reviews to ensure that changes have not caused unintended effects on the baselines (e.g., ensure that changes have not compromised the safety or security of the system).
- Using the <?>, [the ?] with support from <?> is responsible for recording changes to configuration items and reasons for changes as appropriate.
Establish Integrity
- Using the <?>, [the ?] with support from <?> is responsible for recording configuration management actions in sufficient detail so the
content and status of each configuration item is known and previous
versions can be recovered. - Using the <?>, [the ?] with support from <?> is responsible for ensuring that relevant stakeholders have access to and knowledge of
the configuration status of configuration items. - Using the <?>, [the ?] with support from <?> is responsible for specifying the latest version of baselines.
- Using the <?>, [the ?] with support from <?> is responsible for identifying the version of configuration items that constitute a particular
baseline. - Using the <?>, [the ?] with support from <?> is responsible for describing differences between successive baselines.
- Using the <?>, [the ?] with support from <?> is responsible for revising the status and history (i.e., changes, other actions) of each
configuration item as necessary.
Perform Configuration Audits
- Using the <?>, [the ?] with support from <?> is responsible for assessing the integrity of baselines.
- Using the <?>, [the ?] with support from <?> is responsible for confirming that configuration management records correctly identify
configuration items. - Using the <?>, [the ?] with support from <?> is responsible for reviewing the structure and integrity of items in the configuration
management system. - Using the <?>, [the ?] with support from <?> is responsible for confirming the completeness, correctness, and consistency of items in
the configuration management system.
Completeness, correctness, and consistency of the configuration management
system’s content is based on requirements as stated in the plan and the disposition
of approved change requests. - Using the <?>, [the ?] with support from <?> is responsible for confirming compliance with applicable configuration management
standards and procedures. - Using the <?>, [the ?] with support from <?> is responsible for tracking action items from the audit to closure.
Use These Six Steps for Scope Changes on Small Projects
Since small projects are much easier to define and complete quickly, they typically do not have many scope change requests. If scope changes occur, they generally are also small in nature. Even though the changes are small, they still need to be documented and managed.
The following simple process should be used and able to be performed quickly.
- Identify scope change requests. Anyone on the project team can surface scope changes. They should be sent in writing to the project manager by paper, email, etc. No formal form is needed. However, the request must be in writing, not verbal.
- Enter change in Scope Change Log. Even small projects need to track changes.
- Determine the impact of the request. The project manager determines the effect of the scope change on the project in terms of cost, effort, and duration. If there are multiple viable options, the project manager determines their impact as well
- Determine the value of the change. The person that requests the change should also validate the benefits of the change. This may not be a qualitative value for a small project but might be expressed in subjective terms.
- Take the information to the appropriate approver, and the project impact, benefits, and alternatives are taken to the project sponsor (or other designated person) for resolution. The scope request is not pursued if the sponsor does not approve the request and the corresponding impact.
An alternative for small projects is that the sponsor allows the project manager to approve the change. If the project manager declines, the change can still be taken to the sponsor. If the sponsor approves, the project receives schedule/budget relief to work on the change. This would only be the case if the project could still be delivered within the current schedule and budget expectations. - Update Scope Change Log. Update the Scope Change Log with the sponsor decision – accept or decline.
This simple process will ensure you maintain scope control and reduce scope creep – even on small projects.