Detailed Change Control Report: Analysis of Blue Spider Project

This report provides a comprehensive analysis of change control within the Blue Spider Project, addressing key aspects such as identifying required changes, evaluating their impact on project scope, time, cost, and quality. It details the procedures involved in submitting change requests, including the importance of communication, budget allocation, and the involvement of an experienced project manager. The report further explores various options for satisfying each change request, along with the associated risks, and emphasizes the need for a structured approach to change management. The conclusion highlights the significance of effective change management in ensuring project success, referencing the provided change request form for practical application.

Running head: THE BLUE SPIDER PROJECT
The Blue Spider Project
Name of the Student
Name of the University
Author note

1THE BLUE SPIDER PROJECT
Table of Contents
1. Introduction..................................................................................................................................2
2. Discussion....................................................................................................................................2
2.1 Identification of Changes needed in Blue Spider Project......................................................2
2.2 Explanation of Procedures involved to submit a request.......................................................3
2.3 Identifying Change Requests options and involved Risks....................................................4
2.4 The Change Request Form....................................................................................................6
3. Conclusion...................................................................................................................................6
References........................................................................................................................................8

2THE BLUE SPIDER PROJECT
1. Introduction
Change request is a document, which contains a requirement for system adjustment. It is
required for the change management process in any specific project. It provides a clear
knowledge of different objectives to be achieved in the project work (Kerzner, 2017). Change
request takes place when any client wants a change or alteration in their agreed on deliverables.
It also occurs when the project manager is unable to fulfill the initial requirements and includes
new specifications for the work. They have high effect on project scope and budget. The
following report provides brief analyses of the Blue Spider case study with details related to the
changes needed.
2. Discussion
2.1 Identification of Changes needed in Blue Spider Project
The changes required for the project of Blue Spider are provided below:
i) Comprehension of Project Life Cycle: It is required to comprehend the entire project
life cycle, so that they can execute the work within timeline and fixed budget. Moreover, a
proper comprehension of project life cycle would ensure that the project is getting sequentially
(Heagney, 2016). As a result, there would be a positive impact on project scope, time table, cost
and quality. This particular change request would not incur huge cost and project would be
completed within deadline.
ii) Increasing Communication with the Team Members and Client: The second change
request in Blue Spider project is to increase communication with the other team members and
their client. The client was highly dissatisfied with the end result; hence project became a failure

3THE BLUE SPIDER PROJECT
(Meredith, Mantel Jr & Shafer, 2017). Therefore, it is needed to increase communication with
the team members and client for better execution of the work. It will be helpful for the project
budget and scope and end result will be effective.
iii) Proper Coordination of Cost, Time and Specialization for Execution: The project
team needs to have a proper coordination of cost, time and specialization for successful
execution. It would help to ensure that the project results would be in sequence and accurate.
Cost and time management is required for planning and controlling the budget and timeline of
the project work. Gary Anderson, hence should involve a project finance manager, who would be
responsible for identifying any vital change in the time and budget of Blue Spider project.
Moreover, it would have a positive impact on their project execution aspects, such as scope,
time, cost and quality (Schwalbe, 2015). They can use different techniques like changing the
requirements and involvement of new team members in the project team.
2.2 Explanation of Procedures involved to submit a request
The procedures, which should be included during submission of a request for the changes
in Blue Spider case study are as follows:
i) Identifying Requirements for the Change: It is needed to identify the change
requirements, so that the entire team is able to provide proper results to the work. A clear scope
statement helps in providing maximum benefits to the work and the customer is satisfied.
ii) Budget allocation: The second process is to allocate the budget equally, so that every
segment of the project is well executed without much complexity (Heagney, 2016). Moreover, a
sequential approach would be followed in this manner.

4THE BLUE SPIDER PROJECT
iii) Communicating with Client: The third vital process is to communicate with the
client, so that customer satisfaction is kept on top priority and they support approach of Gary at
every phase of the work. Furthermore, a proper communication is also helpful for ensuring that
the requirements and specifications are not changed and project gets completed within time and
budget.
iv) Involving an Experienced Project Manager: Although, Gary had a management
degree, he was inexperienced in his work and hence the project became a failure (Kerzner,
2017). He should involve an experienced manager for the work to make Blue Spider effective.
2.3 Identifying Change Requests options and involved Risks
The options that would be required for satisfying each kind of changes that are requested
are:
1. In the primary stage, the different changes that have been discussed previously would
need to be collected and analyzed. Hence, a particular method needs to be selected based on
which the change requests could be collected (Abrahamsson et al., 2017). This could also be
done in a predictable manner such that it would be helpful for the team and provide a boost
towards the quality and expected outcomes from the project.
2. After each of the change requests have been accumulated, the proper stakeholders
would need to be identified accordingly. Hence, they would need to be allocated to specific tasks
accordingly based on previously established strategies.
3. The project manager and change controller should hold the responsibility to view
whether each of the requested changes are within the scope of the project. Any form of
unnecessary changes should not be accepted or entertained. In case certain changes are being

5THE BLUE SPIDER PROJECT
requested, which are out of scope, the change controller should consult with project manager to
determine whether the requested change would be beneficial towards the project or it would
cause harm towards the business outcomes.
4. The incorporation of the made changes should be made after the change management
team would be aware of the required tasks that would need to be performed for the project. A
responsible project manager would be aware of the various kind of integrations that need to be
performed and incorporated towards the project (Radujković & Sjekavica, 2017). In case any
kind of change requests have been found to be unsatisfactory in nature, it would be the sole
responsibility of the change controller and project manager to act as a medium between the
involved business stakeholders and project management team who would perform the changes
over the concerned project.
5. After the requests for changes have been applied to the project, it would be the
responsibility of the business stakeholders to get a proper view over the changes that have been
made (Qureshi & Kang, 2015). They should understand the outcomes that have been lately
created and ensure that each of the edits that have been done are accurate as per their needs and
standards followed within the business.
As per the various options in relation to change requests being made towards the project,
some of the risks that could accompany are:
1. Some changes might be out of scope and might be detrimental towards the project.
Thus, it would be the sole responsibility of the concerned project manager to ensure that such
changes are not entertained. A proper communication should be made with the person making

6THE BLUE SPIDER PROJECT
the change request and briefed regarding the negative outcomes that might get incurred due to
the implementation of that change within the project.
2. After the application of the required changes within the project, risks might incur that
the stakeholders might not be satisfied with the outcomes and create a chaos with the project
manager and further request for more changes (Yap, Abdul-Rahman & Chen, 2017). Hence,
before the final implementation of changes towards the project, the business stakeholders should
observe over the implementation process and provide their consent. Based on the final consent,
the project manager should proceed over the implementation process.
2.4 The Change Request Form
Please refer to the Change Request Form template
3. Conclusion
From the understanding and discussion of the report, it can be concluded that change
management objectives within the Blue Spider project would be considered to be highly essential
to bring in positive impacts towards the business. The above sections within the report discusses
the importance of making change requests and working on them accordingly. The initial portion
of the report focuses on the identification of changes that would be required during the project
and the kind of impact that would occur over the project scope, time, quality and cost. The report
then emphasizes on the explanation of various processes that would be required for submission
of a change request. Hence, the various options for the satisfaction of the change requests and the

7THE BLUE SPIDER PROJECT
included risks based on making changes have been focused in the report. Based on the
understanding of the case, it can be concluded that the implementation of the required changes
would prove to be highly important and beneficial towards the end results of the project.

8THE BLUE SPIDER PROJECT
References
Abrahamsson, P., Salo, O., Ronkainen, J., & Warsta, J. (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Heagney, J. (2016). Fundamentals of project management. Amacom.
Kerzner, H. (2017). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Meredith, J. R., Mantel Jr, S. J., & Shafer, S. M. (2017). Project management: a managerial
approach. John Wiley & Sons.
Qureshi, S. M., & Kang, C. (2015). Analysing the organizational factors of project complexity
using structural equation modelling. International Journal of Project Management, 33(1),
165-176.
Radujković, M., & Sjekavica, M. (2017). Development of a project management performance
enhancement model by analysing risks, changes, and limitations. Građevinar, 69(02.),
105-120.
Schwalbe, K. (2015). Information technology project management. Cengage Learning.
Yap, J. B. H., Abdul-Rahman, H., & Chen, W. (2017). Collaborative model: Managing design
changes with reusable project experiences through project learning and effective
communication. International Journal of Project Management, 35(7), 1253-1271.

9THE BLUE SPIDER PROJECT