Information Technology Reference
In-Depth Information
These are the sources for origination of change. Now let us look at the reso-
lution of change requests.
8.4 Change Request Resolution
The first response to a CR is to record it in a Change Request Register (CRR) so
that it can be tracked to resolution. A CRR could be as simple as an Excel
Worksheet or a software tool like PMPal that facilitates the functionality of a CRR.
The CRR is the main tool for tracking all CRs to resolution. By recording the CR
in the CRR will ensure that no CR is overlooked/forgotten. It would also enable
tracking every CR to resolution. It would further enable us to analyze the CRs at
the end of the project. The resolution of a change request can be:
1. Accept the CR and implement it immediately
2. Accept the CR but implement it later along with all other CRs
3. Reject the CR
After a change request has been logged in the register, the CR is analyzed by a
PM or a designated person. In large projects, there would be a CCB (Change/
Configuration Control Board) that would analyze the CR and accord approval for
implementation or reject it. In either case, the analysis would determine:
1. Whether the information contained in the CR is comprehensive with all per-
tinent details and facilitates implementation of CR.
2. Whether implementation of CR would be feasible both in technical as well as
financial considerations. When the CR is raised by internal sources such as the
project team or testing team, the analysis would also determine if the imple-
mentation is desirable from a user viewpoint in addition to its feasibility.
3. The amount of effort, cost and calendar time it would consume to implement
the CR.
4. The impact of the CR on the overall project, if it is accepted (especially in
terms of effort, schedule and cost) or rejected (fulfillment of functionality).
Once the analysis is completed, the Impact Analysis would be submitted to
CCB or the PM who would approve or reject the CR. In the case of rejection, the
decision along with reasons for rejection would be communicated to the originator
of the CR and the CR is closed in the CRR. If the CR is accepted, the PM or the
CCB would decide on the strategy for implementation of the CR. Once a CR is
approved for implementation, it would be implemented in accordance with the CR
implementation strategy decided and recorded in the Software Configuration
Management Plan (SCMP). Strategies can include:
1. Implementing CRs immediately on receipt and approval
2. Consolidate all CRs and retrofit them at the end of the project or any another
appropriate point in the development process
Search WWH ::
Custom Search