Software Project Management: ResearchColab- Change Control (Document-10) Presented in 4th year of Bachelor of Science in Software Engineering (BSSE) course at Institute of Information Technology, University of Dhaka (IIT, DU).

1. 1
ResearchColab
Change Control
Team: Reckless 7
Institute of Information Technology
University of Dhaka
25th
November, 2016

2. 2
Contents
Introduction.................................................................................................................................................3
Change Request Process Flow ...................................................................................................................3
Change Control Board ...............................................................................................................................4
Change Request Template: ........................................................................................................................5
Change Log..................................................................................................................................................6

3. 3
Introduction
The Change Management Plan of our project documents and tracks the necessary information
required to effectively manage project change from project inception to delivery. The Change
Management Plan has been created during the Planning Phase of the project and is included in the
planning document.
Change Request Process Flow
Step Description
Generate Change
Request
A submitter completes a CR request and sends the completed request to the
Change Manager
Log Change
Request Status
The Change Manager enters the CR into the CR Log. The CR’s status is updated
throughout the CR process as needed.
Evaluate Change
Request
Project personnel review the CR and provide an estimated level of effort to
process, and develop a proposed solution for the suggested change
Authorize Approval to move forward with incorporating the suggested change into the
project
Implement If approved, make the necessary adjustments to carry out the requested change
and communicate CR status to the submitter and other stakeholders
Change requests are evaluated and assigned one or more of the following change types:
Scope Time Change affecting time Duration Change affecting duration Cost Change affecting
time Resources Change affecting resources Deliverables Change affecting deliverables Product
Change affecting product Processes product Quality Change affecting quality
Type Description
Scope Change affecting scope
Time Change affecting time
Duration Change affecting time
Cost Change affecting cost
Resources Change affecting resources
Deliverables Change affecting deliverables
Product Change affecting product
Processes Change affecting Processes
Quality Change affecting Quality

4. 4
Change requests are evaluated and assigned one of the following status types:
Status Description
Open Entered/Open but not yet approved or assigned
Work in
Progress
CR approved, assigned, and work is progressing
In review CR approved, assigned, and work is progressing
Testing CR work has been reviewed and is being tested
Closed CR work is complete, has passed all tests, and updates have been released.
Change Control Board
Name Position CCB Role
Md. Adiluzzaman Adil Project Manager CCB Manager
Kishan kumar Ganguly
Md. Rakib Hossain
Software Architect & Developer CCB Member
Minhas Kamal
A.H.M. Azimul Haque
Designer & Developer CCB Member
Mostaque Ahmed
Israt Fatema Shantu
Documentation CCB Member

5. 5
Change Request Template:
We have used the following form template for change request:
Change Request
Project: Date:
Change Requestor: Change No:
Change Category (Check all that apply):
□ Schedule □ Cost □ Scope □ Requirements/Deliverables
□ Testing/Quality □ Resources
Does this Change Affect (Check all that apply):
□ Corrective Action □ Preventative Action □ Defect Repair □ Updates
□ Other
Describe the Change Being Requested:
Describe the Reason for the Change:
Describe all Alternatives Considered:
Describe any Technical Changes Required to Implement this Change:
Describe Risks to be Considered for this Change:
Estimate Resources and Costs Needed to Implement this Change:
Describe the Implications to Quality:
Disposition:
□ Approve □ Reject □ Defer
Justification of Approval, Rejection, or Deferral:
Change Board Approval:
Name Signature Date

6. 6
Change Log
Change Log
Project: Network Upgrade Project Date: 04/01/20xx
Change
No.
Change
Type
Description of
Change
Requestor Date
Submitted
Date
Approved
Status Comments
CR001 Equipment This change
request calls
for the
purchase of
wlan routers.
Minhas
Kamal
07/08/16 08/08/16 Denied This request was
denied by the
change control
board because
there is not
adequate funding
available for the
purchase of new
routers and
because the
request is outside
of the project's
scope.
CR002 Schedule This change
request calls
for delaying
the existing
schedule by
one week to
ensure all
applications
are backed up
which was not
considered in
the original
project plan.
Kishan
Kumar
Ganguly
03/11/16 08/11/16 Approved This request was
approved to
ensure the
security and
continuity of all
applications. One
week will be
added to the
project schedule
and the project
manager will
communicate the
impact of this
change to all
stakeholders.