University Name: PROJ6003 Change Management Analysis Report

This report examines change management within the context of the Blue Spider project, highlighting the critical role of effective change control. It identifies key areas where change management was lacking, including product design, communication, and resource management. The report outlines the processes involved in submitting change requests, emphasizing the importance of identifying changes, allocating budgets, and maintaining customer satisfaction. It further explores options for satisfying change requests, along with associated risks such as resistance, leadership deficiencies, and operational disruptions. A change control form is also included. The report concludes that successful project outcomes depend on proactive change management and effective communication, especially leadership skills, and that Gary Anderson's failure to implement these strategies led to the project's downfall.

Running head: CHANGE MANAGEMENT
Change Management
Name of Student-
Name of University-
Author’s Note-

1CHANGE MANAGEMENT
Introduction
Managing the change includes different processes, tools, as well as techniques that are
included for managing the change from the people side for achieving the required outcome from
the project. Change management include change request which is a formal proposal for some
modification in the project (Cameron & Green, 2019). Change request includes when the client
of the project includes some change in the project and that have to be incorporated in the project.
Change management is required in the project because it improves morale of the project,
improves the productivity of the work and also improves the quality of work (Donovan, 2018).
Change management helps to improve cooperation, includes collaboration and also helps to have
proper communication in the project. This project states the change control that was needed for
the Blue Spider Project and processes and techniques that were to be involved in the project to
have a successful project.
Changes required in Blue Spider project
1. Changes related to product design: The product design that was done in the initial
phase of the project to submit the proposal, was to be changed as the product design was not
satisfying the constraints of the project. The requirement of the client was to develop the product
that would work at certain temperature. But to get the project, the proposal was submitted stating
wrong information in the proposal (Alexandrova & Kuzmanova, 2017). That was the first
mistake that was made by the project team. They would have to include change management in
the project to change the design of the product that was to be delivered. The project life cycle
was also to be managed and controlled in the project so that all phases of the project took place
at the scheduled time in the project.

2CHANGE MANAGEMENT
2. Proper communication within the project: Changes was also needed in the
communication process that was included in the project. The communication process of the
project was not controlled properly. Change in communication was also needed in the project as
Gary did not communicated properly with Lord Industries (Croxatto & Greub, 2017). As per
Lord Industries, there was no proper communication between the project team members, the
project manager and Lord Industries. Gary was so busy in doing work by himself, he was not
able to communicate with Lord Industries and that was a problem. Gary would have introduced a
proper communication management strategy as a change in the project and controlling the
communication change would not have resulted in failure of the project.
3. Managing the resources of the project: Change in resource management is another
important aspect that Gary would have introduced in the first meeting when they found out that
they were lagging behind from the project schedule. The project manager had the responsibility
to check on the resources and change it as per the requirement (Ansari, 2019). Resource
management was required as change management in the project to redefine the roles as well as
responsibilities of the team members included in the project. The project manager was also
responsible to provide support to the team members and needed to provide training to the team
members so that they could have performed better.
Processes included in submitting change request
Change management are necessary in a project and those are to be overcome to bring
benefit in the project. This would help to manage the project successfully (Hayes, 2018).
Managing the changes in a project effectively helps in including proper communication, includes

3CHANGE MANAGEMENT
efficiency in the project and provides alignment in providing business goals. For managing the
change request, the following processes are to be followed.
The changes that are to be included in the Blue spider project are to firstly to be identified
(Shafiq et al., 2018). The requirements needed to be changed in the project are to be identified
first before proceeding with the change.
Second change that is included in the project change request is allocation of the budget.
The project budget of the Blue spider project is to be re-designed again to avoid any kind of
complexity in the project.
There should have been a proper communication with the client who were associated
with the project (Pádár, Pataki & Sebestyén, 2017). Proper communication was to be established
in the project so that there would have been customer satisfaction. Customers are the top priority
and they are to be satisfied in the project.
Project manager who was selected for the Blue spider project was to be selected in the
basis of experience. The project manager selected for the project was not experienced and he was
not able to manage the project properly. Gary was good in doing technical work and he liked to
work by himself. He was not able to manage the project. For that experienced project manager
was needed for this project.
Option to satisfy change request and risks involved in Change
Option to satisfy change request are:
1. Requesting the supporting materials: The person who is responsible for the change
request is to be specific in the project (Pollack, 2016). The change request from the person is to

4CHANGE MANAGEMENT
be submitted in written form and that needs to be included in change request form that are
provided. The change request are to be provided in writing and if possible to provide supporting
materials for the change that can help the team members to work with.
2. Determining the change as in scope or out scope: When change is requested by the
client, the project manager needs to identify the change whether it is in the scope or out of scope.
Simultaneously change will be carried out in the project.
3. Having a team accessing the priority of change: The risks that are included from the
change are to be determined before implementing them in the project. This would help to
determine the change without any risks.
4. Approve and reject the change: Approving and rejecting the change is required in the
change management (Badewi, 2016). If the change is accepted, them work is proceeded
accordingly. And if it is rejected, the change is to be rejected providing proper risks.
5. Deciding the course of actions that are to be taken: After approving the change, the
actions that are be taken in completing the change are to be determined in the project.
Risks included in change management are:
Resistance: Resistance in change is a common factor and that brings risks in the project.
(Ng, 2018) There always remain a risks that the project team members cannot accustom with the
change in the project.
Leadership: Change in a project needs leadership and project manager not having
leadership skill will not be able to manage the project. (Rasnacis & Berzisa, 2017) Leadership in
project manager helps to manage the change efficiently.

5CHANGE MANAGEMENT
Disruption: There might be operational disruption in the project with change request in
the project. Proper implementation of the project is to be included in the project.
Change Control Form
Conclusion
The project above states the change control that was needed for managing the Blue
Spider project. The project was a big failure as the project manager was not able to manage the
project properly. Change management or change control helps to complete the project
successfully and that would help to successfully manage and control the project. The change
management in the project would ensure the behavioral changes that would help in resulting as
well as working towards to fulfilling the goal of the project. The culture and the mode of the
project changes dues to change management included in the project. Change management is not
very easy and Gary Anderson managing the Blue Spider project needed to manage the changes
and manage communication in the project. This report details the change control and the change
management that were to be undertaken by the project manager for handling the Blue Spider
project.
change
request.docx

6CHANGE MANAGEMENT
References
Alexandrova, M., & Kuzmanova, M. (2017). Change Management and Project Management
Integration: Survey Evidence. Leadership & Management: Integrated Politics of
Research and Innovations, 204.
Ansari, R. (2019). Dynamic Simulation Model for Project Change-Management Policies:
Engineering Project Case. Journal of Construction Engineering and
Management, 145(7), 05019008.
Badewi, A. (2016). The impact of project management (PM) and benefits management (BM)
practices on project success: Towards developing a project benefits governance
framework. International Journal of Project Management, 34(4), 761-778.
Cameron, E., & Green, M. (2019). Making sense of change management: A complete guide to
the models, tools and techniques of organizational change. Kogan Page Publishers.
Croxatto, A., & Greub, G. (2017). Project management: importance for diagnostic
laboratories. Clinical Microbiology and Infection, 23(7), 434-440.
Donovan, G. O. (2018). Creating a culture of partnership between Project Management and
Change Management. Project Management World Journal, 7(1), 1-11.
Hayes, J. (2018). The theory and practice of change management. Palgrave.
Ng, J. J. (2018). A deeper look into a project management tool: The change register. IEEE
Engineering Management Review, 46(1), 24-26.
Pádár, K., Pataki, B., & Sebestyén, Z. (2017). Bringing project and change management roles
into sync. Journal of Organizational Change Management.

7CHANGE MANAGEMENT
Pollack, J. (2016, December). The need for integration between organizational project
management and change management. In 2016 IEEE International Conference on
Industrial Engineering and Engineering Management (IEEM) (pp. 1245-1249). IEEE.
Rasnacis, A., & Berzisa, S. (2017). Method for adaptation and implementation of agile project
management methodology. Procedia Computer Science, 104, 43-50.
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.