2. Change Control
2. Change Control
PROCESS
Software Engineering-II (SE-406)
There are 5 core steps that form a typical project change control
process
Project
Change
Control
IDENTIFY PROJECT CHANGE
The PMO can help ensure that all reviewers complete their reviews
by the deadline.
If not this will delay when the change request can go forward for
formal approval.
Review completion
When all parties have reviewed and provided feedback, the change
request is ready to go for formal approval.
REVIEW PROJECT CHANGE
All project change requests must have a decision of either approve or reject.
Approve / reject process
The process is very simple.
All stakeholders required to make the decision need to have the change
request details shared with them so they can make a decision.
It is important that the process is documented including, how a decision can
be made.
For example what if there are 10 stakeholders who need to make the
decision.
If 6 vote “yes” is that sufficient? What happens if 5 vote “yes” and 5 vote “no”?
Who is responsible for a deciding vote?
APPROVE/REJECT REQUEST
The project change control process is not complete until the required
change has been incorporated into the scope of the project.
Implement project change request process
Ensure that the change request template and any supporting
information is stored so that there is a record of what information was
used to reach the decision.
Ensure that the decision from the Change Board is clearly
communicated to all relevant stakeholders.
This is especially important for the project manager / project team
who needs to implement the change.
IMPLEMENT PROJECT CHANGE REQUEST