Blue Spider Project Analysis: Park Corporation's Change Management

This report provides a detailed analysis of the Blue Spider project managed by Park Corporation, focusing on project management challenges and change control. The report examines issues such as poor communication, leadership problems, and inadequate functional support, which led to project failures. It covers the change control process, change identification, and impact analysis, highlighting the risks and mitigation strategies. The study also addresses organizational changes and communication breakdowns, offering recommendations to improve project outcomes. The report's structure includes an executive summary, table of contents, introduction, case study overview, discussion of project management issues, change control, risk mitigation, organizational changes, recommendations, and conclusion. The report emphasizes the importance of effective communication, clear roles and responsibilities, and proper risk management in ensuring project success, providing insights into the complexities of project execution and control within a project-based organization. The appendix includes change request forms, change logs, and change management plans.

Running head: PROJECT MANAGEMENT
PROJECT MANAGEMENT
Name of the Student
Name of the University
Author Note:

1PROJECT MANAGEMENT
Executive Summary
The study focus on the evaluation of attempts made by Park Corporation in order to handle Blue
Spider project. This merely highlights any kind of constraints with the team members which
includes program. It merely encounters in the whole process of understanding the goals and
objectives. The report focus on narration of different factors impending parks from delivering
what is expectation of client. It merely takes up complete program from the perspective of leader
and team members. This merely stand out to the successful completion of project which require
handling to promote the stakeholder participation.

2PROJECT MANAGEMENT
Table of Contents
1. Introduction................................................................................................................3
2. Case Study Overview................................................................................................3
3. Project Management Issues.......................................................................................4
4. Change Control..........................................................................................................5
5. Change Identification.................................................................................................5
6. Change Impact analysis.............................................................................................6
7. Proposed changes risk mitigation..............................................................................7
8. Organizational Changes and Communication...........................................................7
9. Recommendation.......................................................................................................8
10. Conclusion.................................................................................................................9
11. References................................................................................................................10
12. Appendix..................................................................................................................12
Change request form..........................................................................................................12
Change Log........................................................................................................................14
Change management plan..................................................................................................16

3PROJECT MANAGEMENT
1. Introduction
The following report deals with an approach taken by Park Corporation, which stands out
to be a Project-based firm. The organization was involved in execution of research and
development of Blue spider project. In the year 1975, the corporation accepted the point that
there is a need for change in Corporate Strategy (Butt & Jamal, 2017). By using a new strategy,
the park began to speed up its R&D department. This particular project focus on enhancing the
structural capability of the Missile. The whole analysis focus on complete evaluation of
approaches related to project management taken by the firm. It is completely related to project
failure and satisfying the need of customer (Dawood, Siddle & Dawood, 2019). There is a list of
recommendation which will help in keeping track of Park Corporation movement for becoming a
project-oriented- organization.
The report provides an overview of the required changes in the case study. The next part
deals with the effect of change on the project. The report deals with a list of steps involved in
requests to deal with required changes.
2. Case Study Overview
Park Corporation is known to be project-based firm involved in complete project
execution related to R&D. With the help of necessary steps, Park Corporation come up with the
plan of completing the first stage of this blue spider project. Lord Industries stand out to be prime
contractor for this Army Spartan Program. The upper management of this organization does not
want lose the golden chance and even risk the chance by providing false the technical details. All
these was done to win the bid and entering into business.

4PROJECT MANAGEMENT
There was project manager with background in research and development. He was
assigned in order to support project even the engineering manager stand out to be completely
reluctant for their people in particular. Considering the shortcomings, the project was started. All
the customer requirements of the project were not met, and number of discussion done. Park
corporation need to spend much of its time in allocating project, and customers even threaten to
stop the project. Team member on this project and project manager were completely frustrated.
As a resulted of limited expertise in the domain of skills in project management, he could not
have much enhanced controlling of situation.
3. Project Management Issues
Some of the issues which were encountered with this blue spider project were poor
communication, poor skill in negotiation, leadership behavior problem, poor functional support,
and improper way of handling conflict.
In this case study, functional manager selects program manager for the given project. The
whole thing was carried out in with no consultation with program director. The project
management guidelines are not being followed. Gary is very good production engineer and
capable of taking up the responsibilities of project manager. The organization even claimed that
matrix structure, and that is not completely functional for this blue spider project. Gray was not
completely clear regarding complete understanding of duties within blue spider project.
Park Corporation does not have good Human resources to follow. Gray was promoted to
the post of Project Manager without any kind of induction. Right after the proposal plan, it had
very poor support from functional management. Gary put all the pressure on driving and does not
making use of team in effective way. He does not have good balance in between technical and

5PROJECT MANAGEMENT
administration for responsibilities. Considering the threats from Lord Industries in order to
establish an office of Park Corporation. It merely highlighted a lack of complete trust among the
people.
4. Change Control
It can be defined process in project management which highlights the required changes in
the project. This needs to be completely defined, reviewed and completely approved prior to its
implementation. Change control process helps in avoiding any kind of unnecessary changes
which can disrupt the given services in blue spider project. In addition, it also ensures effective
and efficient use of resources.
5. Change Identification
Gary lacked some of the necessary skills and experience to head this kind of project. In
some of the decisions and areas, Gary come up with error as the whole project was hit list of
issues. These problems stand out to be a mixture of skill and experience. Gary focused too much
on the R&D and administrative work at the expense of important areas (Perrotta et al., 2017).
Gary emphasized on some error in terms of financial planning. His team implemented the plan
‘B’ when the formal was rendered void as a result of predictable possible changes. Gary lacked a
strategy of clear communication. It ultimately resulted in clear communication with Lord.
As soon as the project proceeded, the customer relationship began to change into sour.
The customers understand the point that the project was not implemented as per the provided
outline. The customer also faced that there was a miscommunication in the department. It offered
clear idea regarding proceeding of customer in order to advise Gary (Aguilar et al., 2016). This
merely focus on refrain from any kind of technical mix up and administrative responsibilities.

6PROJECT MANAGEMENT
Right from there, customer come up with a plan of effective change in the whole project. All the
changes highlighted that project management team needs to incur some extra costs. It is due to
the point that customers completely refused to cater to any kind of additional expenditure.
Technical details highlighted the point that all components need to operate in a normal
and successful way in-between temperature range of 650F and 1450F. But the testing highlighted
that the design parts were unable to function above 1300F (Anushree, Velugula & Prasad, 2017).
In the meeting prior to the submission of the final proposal, Gary highlighted some points which
need to be covered like
 Change in design material
 Incorporation of new materials for the project.
6. Change Impact analysis
Scope change request is merely required for either subtraction or addition upon the scope
of the work, which has been agreed for the project. Scope change request can be easily managed
for being a part of earlier defined scope. All these thing are completely outlined for being a part
of the project plan (Peacock & Sethu, 2017). The process helps in analyzing required changes
that are approved by project manager. It requires the involvement of the necessary authority
needed for supporting other changes. The overall success of the project depends on both
controlling and project scope management. Change in scope can impact other parameters like
quality, risk, and schedule of project.
In project management change request can be used for identifying the required change in
the project. In project, change come up in different size and shape. The project manager keeps a
track of list of steps and avoid steps in order to avoid project combustion (Policy, 2018). Most of

7PROJECT MANAGEMENT
the organization provide change request in a different way. In this case, change order request
stand out to be a simple tool which is used for documentation and keeping track of ongoing
change.
The addition of new material to project can result in administrative errors to this blue
spider project. If still the project experiences overruns in project administration, which not
speeding up the progress of the project (Groth & Brunsmeier, 2016). Even some small issues in
between the administrative team can become catastrophic.
Making changes in the design materials can result in the re-opening of the project when
there is a problem with quality. This in turn increases the overall cost for the project which will
be increased to large extent (Kerzner, 2017). Responsibility completely lies within the project
manager for preventing any kind additional due to poor quality materials.
7. Proposed changes risk mitigation
There are large number of risk associated with change request like
Resistance to change: Resistance to change stand out to be as one of the biggest reason
behind the failure of change request. Most of the team members of this project fear to change as
they are not familiar with this process (Anushree, Velugula & Prasad, 2017). There are list of
ways for combat the resistance to change. One of the most suitable ways is that the employees
see management is committed to ensuring the changes.
Scoop Creep: In most of the project, scope creep stand out to be as one of the biggest
risk. It requires the involvement of project scope over the period of time. It stand out to be
biggest threat in change request (Peacock & Sethu, 2017). In order to tackle the scoop creep in
change request, the scope needs to be changed, as mentioned.

8PROJECT MANAGEMENT
8. Organizational Changes and Communication
Matrix organization structure in the domain of project management provides organization
with leverage in the way pool of skills. This is merely available in various functional zone of
business along with maintaining the cost base. Considering the same viewpoint, Park
Corporation had adopted the structure by making use of multi-disciplinary team members like
research and development like Quality control, manufacturing, finance, and purchasing.
All the things were unclear or authority which is given to project manager. Gray
Anderson come up with full fledge like project manager which highlights imporper definition for
roles and responsibilities of each members of project. The accountability of project manager
need to focus on cost and project quality. The project manager need to focus on some of
technical areas and makes report on engineering management. It merely indicates a gap in
organizational structure to meet the objective of project.
Effective Communication can be stated as important process for handling project in this
nature. It merely makes the project leader to be completely focused on the way of achieving
proper communication. Development and implementation of effective communication process
make it easy for analyzing any kind of misunderstanding which highlights smooth flow of
activities. With respect to communication at Park Corporation, it merely allow the employees of
customer and collector to establish communication without passing through project office easily.
9. Recommendation
There is a list of recommendation for blue spider project like

9PROJECT MANAGEMENT
 This project require complete definition, which comprises of project scope, defined
deliverables, both functional and project requirements, acceptance criteria from different
customers. There is need for drawing up WBS and communicating it to various parties.
 Gary Anderson does not a complete understanding with respect to role in this project.
Gary come up with new way in order to have program management.
 Risk management control will play a key major part in different part of the case study
which are both risks that is internal and external.
 Gary does not communicate well in this project that with external and internal resources.
Gary need to formalize the communication to the thing which happen on project by
making project communication plan.
10.Conclusion
The report is all about change management in the blue spider project. Park Corporation
decided to complete the first phase of the project, which stand out to be a R&D project. The
focus of the project is all about enhancing the capabilities of the structure of Spartan missile.
Lord industries stand out to be main contractors for the Army Spartan program. The organization
was interested in this project as it will merely lead to 500 million programs spread in just 20
years. The upper management of the organization is unwilling to lose this project at any cost.
The organization even risked its overall reputation. Avoiding false technical details in order to
win the bid for the project. In the last section, a change request form has been provided, which
can be used in the workplace.

10PROJECT MANAGEMENT
11.References
Aguilar, J. A., Tripp, C., Zaldivar, A., Garcia, O., & Zurita, C. E. (2016). Evaluating a
requirements change request in a goal-oriented requirements engineering model. IEEE
Latin America Transactions, 14(5), 2411-2417.
Anushree, J. V., Velugula, N., & Prasad, K. N. P. (2017). Design of an ERP Software that
Facilitates Easy Flow of a Process Change Order (PCO) Request in an
Enterprise. International Journal of Engineering Science, 12771.
Butt, S. A., & Jamal, T. (2017). Frequent change request from user to handle cost on project in
agile model. Proc. of Asia Pacific Journal of Multidisciplinary Research, 5(2), 26-42.
Dawood, H., Siddle, J., & Dawood, N. (2019). Integrating IFC and NLP for automating change
request validations. Journal of Information Technology in Construction, 24, 540-552.
Fleming, Q. W., & Koppelman, J. M. (2016, December). Earned value project management.
Project Management Institute.
Groth, M., & Brunsmeier, A. (2016). A cross-sectoral analysis of climate change risk drivers
based on companies' responses to the CDP's climate change information request (No.
364). Working Paper Series in Economics.
Kerzner, H. (2017). Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons.
Marchewka, J. T. (2016). Information technology project management: Providing measurable
organizational value. John Wiley & Sons.

11PROJECT MANAGEMENT
Meredith, J. R., Mantel Jr, S. J., & Shafer, S. M. (2017). Project management: a managerial
approach. John Wiley & Sons.
Peacock, J., & Sethu, H. (2017). Which Request Creates the Most Diet Change: A Reanalysis.
Perrotta, D., Faria, J., Araájo, M., Tereso, A., & Fernandes, G. (2017, December). Project change
request: A proposal for managing change in industrialization projects. In 2017 IEEE
International Conference on Industrial Engineering and Engineering Management
(IEEM) (pp. 1525-1529). IEEE.
Policy, C. P. (2018). History of most recent policy changes: Version Date Page Change Origin of
change eg BCT request, change in legislation. Policy, 3, 20th.

12PROJECT MANAGEMENT
12. Appendix
Change request form
Change Request
Project: The Blue Spider Project Date: 15/03/2020
Change Requestor: Change No:
Change Category:
 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:
For this blue spider project, there are list changes required for the project like
 Changes in the design materials
 Implementing new materials for the project.
Describe the Reason for the Change:
The material used in this project were of below standard. During testing it was
highlighted that design parts were unable to function above 1300F.
Describe all Alternatives Considered:
Team in charge for the blue spider project at Park, tried to deal with the risk in all
possible ways. The group tried to deal with the possible risk in best ways.
Technical Changes Required for this Change:
During the testing phase, it was highlighted that design parts were unable to function
above 1300 F. But it was clearly stated that the successful range of temperature lied in between
650F and 1450F.

13PROJECT MANAGEMENT
Risk associated with the change
There are mainly two risk involved in this project
 Scoop creep
 Resistance to change.
Quality Implications :
The suggested changes will ultimately help in improving the overall quality of project.
Disposition:
Approve □ Reject □ Defer
Justification of Approval, Rejection, or Deferral:
The blue spider project lacks in some of the areas. The suggest changes will help in
tackling those particular areas.
Change Board Approval:
Name Signature Date

14PROJECT MANAGEMENT
Change Log
Blue Spider Project Change Log
Project Name : The blue Spider Project Project Sponsor :
Seri
al
No.
Origina
tor
Descripti
on of
Change
Date
received
Date
required
Scope
Impact
Schedule
Impact
Spendi
ng
Impact
Appro
ved
1 Project
Manag
er
Change in
design
material
15/03/2
020
17/03/2
020
Change
in design
material
will
affect the
project
scope
The
project
will be
delayed
due to
changes.
The
budget
of
project
will be
impact
to
large
extent.
Yes
2 Project
Manag
er
Incorpora
tion of
new
material
15/03/2
020
17/03/2
020
The
scope of
project
will be
affected
as result
of
incorpora
Incorpora
tion of
new
material
will result
in
changes
in project
Addin
g new
materi
al in
this
project
will
result
Yes

15PROJECT MANAGEMENT
tion of
new
material
schedule. in
increas
e in
project
budget
.

16PROJECT MANAGEMENT
Change management plan
Stages Objective Main objective Output
Taking necessary
Preparation for
change
Accepting the
required change in
this specific project
Defining the change
management strategy
Developing a model
of sponsorship
Change
characteristics profile
Organizational
attributes profile
Managing all the
required change
Creating a plan
which needs to be
integrated into this
project activities
followed by
implementing it
Developing change
management plan
Taking right action
and implementing
suitable plan
Communication plan
Plan for proper
training
Resistance
management plan
Reinforcing all
change
Creating a specific
function for ensuring
that change is
completely
sustained.
Collecting and
analyzing all the
required feedback
Implementing
corrective actions.
Compliance of audit
reports
Recognition of
approaches