PROJ6003: Project Execution and Control - Change Management Report

This report delves into the critical role of change management within project execution and control, drawing upon the provided case study of the Blue Spider project to illustrate key concepts. It highlights the necessity of change management for ensuring project success, emphasizing that changes are inevitable and must be proactively managed. The report discusses the consequences of inadequate change management, as demonstrated by the Blue Spider project's failure due to poor handling of cost increases and communication breakdowns. It explores different types of change requests (inside and outside scope), processes for identifying and managing them, and the importance of clear communication and approval protocols. The report references relevant literature to support its arguments, providing a comprehensive overview of change management strategies and their impact on project outcomes. The report suggests that effective change management involves implementing the right processes to mitigate risks and ensure project goals are achieved.

Running head: PROJECT EXECUTION AND CONTROL
Project Execution and Control
Name of Student-
Name of University-
Author’s Note-

1PROJECT EXECUTION AND CONTROL
Necessity of Change management in project management
Change management includes managing the change for ensuring behavioral outcomes
that results to ensure the goal of the project. Because of change management, the culture of the
organization and the way of operating a project also changes (Ansari, 2019). Every project
manager knows that at some point in project life cycle, there is a need of change in all projects.
Project managers expects changes in a project and those changes are to be managed in successful
completion of the project. Change management can be stated as process, technique and tool that
helps to manage the change that are made by the people or the client to take the business
outcome. It includes systematic management of employee engagement as well as adoption when
changes is required in the organization. Change management mainly helps to embrace the
change, utilize it as well as adopt the change in daily work.
Key issues in case study that lead to necessary changes
In the Blue Spider project, change management was necessary to be successful in
completing the project. This project was not successful as Gary was not able to manage the
change in the project. If change management was undertaken in the project, then the project
would have been successful. Gary was not able to manage the increased cost of the project and
the change in the testing phase of the project was also not informed to the Lord Industry. Henry
was also responsible in not letting Gary to communicate properly with the Lord Industry about
the changes they are including in the project. This has led to project failure and result in huge
loss for the Perks Corporation.
Change request is basically a proposal that is done to change a particular system or a
product. Change request are bought from the client. But in the Blue Spider project, change

2PROJECT EXECUTION AND CONTROL
occurred from Perks Corporation and was not informed to the client as well. In the project,
Change request could have been incorporated in two different ways: one is inside the scope and
the other is outside the project scope. For Blue spider project, inside scope would include all
small corrections that the client needed for the Spartan project. With the inside change scope, the
budget would also have not increased in the project (Shafiq et al., 2018). If Gary would have
implemented change request outside the project scope, that would not have let to increase the
project completion time and they could have proper budget on the project.
Processes to identify change request in the case study
For managing the Blue Spider project, some tips were to be followed and those are stated
below.
1. Gary should have requested supporting materials to make the changes in the project.
2. The change should have been determined first, that is inside scope change request or
outside scope change request.
3. Getting approval for the change request that is to be included in the project.
4. The course of action for the project is to be decided before.
It can be concluded that for any project, handling the changes in a project should include
implementing the right processes in the right place so that it can be managed effectively.

3PROJECT EXECUTION AND CONTROL
References
Ansari, R. (2019). Dynamic Simulation Model for Project Change-Management Policies:
Engineering Project Case. Journal of Construction Engineering and
Management, 145(7), 05019008.
Shafiq, M., Zhang, Q., Akbar, M. A., Khan, A. A., Hussain, S., Amin, F. E., ... & Soofi, A. A.
(2018). Effect of project management in requirements engineering and requirements
change management processes for global software development. IEEE Access, 6, 25747-
25763.