Scope verification involves formalizing acceptance of the project scope. Key project
stake holders, such a customer and sponsor of the project, inspect and then formally
accept the deliverables of the project during this process. If the deliverables are not
acceptable, the customer or sponsor usually requests changes, which result in
recommendation for taking corrective actions. The main outputs of this process,
therefore, are accepted deliverables , requested changes , and recommended corrective
actions.
Where as scope control involves controlling changes to project scope, which is a
challenge on many information technology projects. Scope control includes identifying,
evaluating, and implementing changes to project scope as the project progresses. Scope
changes often influence the team’s ability to meet project time and cost goals, so project
managers must carefully weigh the costs and benefits of scope changes. The main outputs
of this process are requested changes, recommended corrective actions, and updates to
the project scope statement, WBS and WBS dictionary, scope baseline, project
management plan, and organizational process assets.
There were multiple additions or changes to the project because of the review by the
Sponsor in this project VP and client service representative has reviewed the mock ups
designed for the site and the list of the video games that will sold which has been
formulated with the help of Edsys there were some 4 changes that have been requested.
As Project manager I have requested the sponsors to document their change requests in
the change request form shown below providing as much information as possible so that
the changes are tracked by me(project manager) in the change tracking tool Rational
ClearQuest and also the changes are adjusted in scope and project schedule after revising
the costs and effect of change on schedule and scope.
Video game delivery project- Change Request
Prepared By:
CR #:
Date Submitted:
Title
Enter a brief, descriptive name for this change request.
Priority
Use a one or two word description of the change request priority (e.g., Top, High,
Medium or Low).
Change Request Details
Description
Describe the change being requested. Include a description of impacts to
existing objectives and deliverables as well as any new objectives and
deliverables.
Justification
Provide a business case for the change being requested.
Impact if not implemented
Describe the impact if the requested change is not implemented as requested.
Discuss any issues of timing of implementation.
Change Request Impact Analysis
Scope & Requirements
Describe the impacts on project requirements including whether this is in or out
of scope of the project as required.
Project Risk
Describe risks associated with this change or overall impacts of change on
project risks.
Schedule
Describe potential impacts of change on project schedule. Include description of
proposed implementation schedule associated with this change.
Budget
Include information about impacts on project budget. Provide specific details on
costs associated with the change.
Project Management
Describe any impacts to the project management plan or project organization.
Alternatives
Describe alternatives to the proposed change.
Recommendation
Include a recommendation of proposed action based on recommended change and
impacts.
Resolution Description
Include information about what is to happen with this change request (e.g., approved,
denied, on hold, etc.), the date this decision was made, who was involved in the decision
and the rationale for the decision.
Request Implementation Activities
Describe specific follow-on activities required by the resolution, assigned resource,
timeline and other details. Include references to modifications to the project schedule
and project or project management deliverables as appropriate.