PROJ6003 Project Execution and Control: Blue Spider Project Report

This report analyzes the Blue Spider Project, focusing on project control and change management within the context of Park Corporation's research and development initiatives. The report identifies required changes in the project, particularly concerning design material limitations and communication breakdowns. It assesses the impact of these changes on project scope, time, quality, and cost, exploring techniques for effective management. The analysis includes a detailed examination of change request procedures, outlining the steps involved and the risks associated with each change, such as potential loss of vital information. A change control form is provided to document and manage modifications, ensuring that all aspects of project performance are properly addressed. The report concludes by highlighting the importance of effective communication, cooperation, and the application of project management strategies to mitigate risks and improve project outcomes. References to relevant academic sources are also provided.

Running head: PROJECT CONTROL
PROJECT CONTROL
(The Blue Spider Project)
Name of the Student
Name of the University
Author Note:

1PROJECT CONTROL
Table of Contents
Introduction..........................................................................................................................2
Required Changes for the Blue Spider Project....................................................................2
Impact on Project and Techniques for managing them.......................................................3
Steps for change request......................................................................................................4
Option associated with each change and risk associated with it.........................................5
Change Control Form..........................................................................................................6
Conclusion...........................................................................................................................7
References............................................................................................................................8

2PROJECT CONTROL
Introduction
Park Corporation is very much associated with research and development business,
carrying out project works for defense. In the last few years, it has completely changed its
business and merely focuses on research and development for the facility of low-cost production.
Considering the viewpoint of salary offered by Park Corporation, there was limited access to
different experienced engineers, so they employed only inexperienced engineers (Perrier,
Benbrahim & Pellerin, 2018). Gary stand out to be an outstanding production engineer and was
promoted to senior post, responsible for different R&D activities. In the year 1978, Park
Corporation come up with idea of biding the very first stage of Blue spider project. The point
needs to be considered that lord industries stand out to be main contractor for this Spartan
program.
All the required changes in case study has been identified. An analysis has been done
regarding its impact on scope, cost, time, quality, and cost of project and techniques needed for
managing it. The step of submitting change request has been discussed in brief.
Required Changes
For this blue spider project, Gary Anderson was chosen by Director of engineering to
lead the project due to his R&D background (Martinsuo & Hoverfält, 2018). If this particular
research and development program has been finalized in successful way, then blue spider project
will have potential in the upcoming years. Gary Anderson come up with team from different
department of organization for supporting this project.
All the technical components of this project were able to operate in normal way in
between a temperature range of 650F and 1450F. The present testing highlights that design of

3PROJECT CONTROL
Park Corporation design would not function right above 1300F. There was an ongoing R&D
effort conducted in the upcoming weeks. In this proposal, Gary Anderson highlights some areas
which require changes like change in design materials or addition of new materials in this project
(Gaber, Mazen & Hassanein, 2016). In addition, he highlighted that the project should go with
proposal without providing information to customers.
Both lack of consultation and poor communication can easily hamper the overall
effectiveness of team progression. Gary Anderson failed to inform its team members regarding
performance of this blue spider project and only approached them when there was challenges
(Mikkelsen, 2018). Improper communication among the department stand out to be main cause
behind the overburden. The blue spider project faced communication breakdown on both the
level that is internally and with the client.
Impact on Project and Techniques for managing them
These suggested changes will have a huge impact on scope, time, quality, and cost for
this project. Project scope of this blue spider project completely deals with some particular
requirements or even takes up necessary step for completing this project (Frimpong & Oluwoye,
2018). Scope stand out to be an important factor in managing project that whether they agile
software projects or waterfall project. Scope management stand out to be an important factor in
managing scope as it helps in assigning resources in effective way. Another factors which comes
into picture at the time of handling scope is expectation of stakeholders. It is specifically used for
long term projects where stakeholders are introduced in the middle of project.
Schedule is stand out a time which has been estimated for completing the given project. It
ultimately result in completing the project and providing the right deliverables. Work Breakdown

4PROJECT CONTROL
structure is merely used in order to have goal of large project. It is all about breaking the project
into series of tasks. After this, all the given task are given priority linking the dependencies.
Right after this, it is place on the timeline (Kerzner, 2017). Changes in schedule of this project
can be tracked by making use of work breakdown structure and Gantt chart. The main function
of WBS is all about breaking the project into series of manageable task. While Gantt chart is an
effective way to keep a track of schedule within this blue spider project.
Financial aspect of this blue spider project is based on different parameters. There is
involvement of various resources, material to people, which is inclusive of material and people
cost associated with labor (Cooper & Sommer, 2018). There are many forces from outside which
can impact the project, and it should be taken into consideration like cost associated with work.
There are mainly two kind of cost that is variable and fixed for this blue spider project.
Project quality management is merely inclusive of both process and activities needed by
the performing organization which analyze the overall quality policies, responsibilities for
project (Meredith, Mantel Jr & Shafer, 2017). Blue spider project needs to implement quality
management system in its policy and procedure for overall improvement.
Steps for change request
Change request in blue spider project can bring huge number of benefits. There are
mainly five steps of change request like
Requesting for any supporting materials: All stakeholders of this change requests
regarding this blue spider project need to be completely specific and explicit in nature
(Demirkesen & Ozorhon, 2017). The person asking for change need to clear with respect to
anticipated benefits for this project.

5PROJECT CONTROL
Analyzing whether change request for scope: There is always need for thinking
regarding scope of change request (Kerzner, 2017). The team completely decides to implement
the provided changes.
Team assess the priority of change request: The opinion of the people needs to be taken
into account for changes within project. It is responsibilities of the team members to have
complete idea regarding any kind of risk.
Approving or Rejecting change Request: Team can either have approve or change
request after its impact on project (Marchewka, 2016). There is a list of methods involved in
having approval process for most of the organization.
Making a decision and course of action: All the deliverables of the project need to be
updated on regular basis after when the request of change has been approved (Varajão, Colomo-
Palacios & Silva, 2017). This should need to include different plan and schedule and work
related to business.
Option associated with each change and risk associated with it
There are mainly five steps involved in satisfying each change request like
 Request to make changes within this blue spider project
 Updating the change log
 Accessing the priority for change request
 Accessing all the required change.
The risk associated with change requests like

6PROJECT CONTROL
Loss of Vital Information: Change request is possible due to loss of important
information during the process of conversion. The change merely requires involvement of
software or change in material of project (Martinsuo & Hoverfält, 2018). By making use of
project management strategies, the overall risk can be tackled to a large extent. Project team
members must back up some of the vital data of this project. There is a need for ensuring the
effective plan for change management regarding how the conversion will be handled.
Change Control Form
Change Request Form
Project: The Blue Spider Project Date: 29/03/2020
Change Requestor: Change No:
Change Category:
 Schedule Cost  Scope  Requirements
□ Testing □ Resources
Change Affect
□ Corrective Action □ Preventative Action Defect Repair
 Updates
□ Other
Change Requested:
The project lack some of the basic criteria to fulfill the requirements of customer. The project
has certain technical errors which can be overcome by using standard quality materials.
Reason for Change:
The blue spider project lacks standard quality materials. In order to meet the basic technical
requirement, the project needs to have standard quality materials.
Technical Changes
The design materials of this project lack standard temperature requirement. The designed
material were unable to perform over 1350 F.

7PROJECT CONTROL
Risk associated with the change
The risk associated with this change request are loss of important information
Quality Implications :
It is expected that if the change request is followed in proper way, then it will improve the
overall quality of blue spider project.
Disposition:
Approve □ Reject □ Defer
Justification of Approval, Rejection, or Deferral:
Change Board Approval:
Name Signature Date
Conclusion
The above section helped in analyzing the point that the report focus on matrix project
management organization used by the Park Corporation on this Project. It was known to be
multi-disciplinary team having team members from various background. The project
management of this project was completely responsible for performance of individual steps
needed for accomplishing the work. The working members on this project had two bosses if they
need to work on more than project. If the key players have an idea regarding the conflict between
Anderson and functional manager, then it can reduced to large extent. The overall success of this
blue spider project was based on Anderson ability and cooperation with functional managers.
There was either no or very little understanding of relationship which exist between Anderson
and other team members. The report provides an identification of each change request and risk
associated with that particular option. In the last part, a change control has been given for this
project.

8PROJECT CONTROL
References
Cooper, R. G., & Sommer, A. F. (2018). Agile–Stage-Gate for Manufacturers: Changing the
Way New Products Are Developed Integrating Agile project management methods into a
Stage-Gate system offers both opportunities and challenges. Research-Technology
Management, 61(2), 17-26.
Demirkesen, S., & Ozorhon, B. (2017). Impact of integration management on construction
project management performance. International Journal of Project Management, 35(8),
1639-1654.
Frimpong, Y., & Oluwoye, J. (2018). Project Management Practice in Groundwater Construction
Project in Ghana. American Journal of Management Science and Engineering, 3(5), 60-
68.
Gaber, A. M., Mazen, S., & Hassanein, E. E. (2016). Comparative Study for Software Project
Management Approaches and Change Management in the Project Monitoring &
Controlling. International Journal of Advanced Computer Science and Applications, 7,
259-264.
Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring
and monitoring project performance. John Wiley & Sons.
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.

9PROJECT CONTROL
Martinsuo, M., & Hoverfält, P. (2018). Change program management: Toward a capability for
managing value-oriented, integrated multi-project change in its context. International
Journal of Project Management, 36(1), 134-146.
Meredith, J. R., Mantel Jr, S. J., & Shafer, S. M. (2017). Project management: a managerial
approach. John Wiley & Sons.
Mikkelsen, M. F. (2018). Projects, success, and complexity. International Project Management
Association Research Conference 2017, UTS ePRESS, Sydney: NSW.
Perrier, N., Benbrahim, S. E., & Pellerin, R. (2018). The core processes of project control: A
network analysis. Procedia computer science, 138, 697-704.
Varajão, J., Colomo-Palacios, R., & Silva, H. (2017). ISO 21500: 2012 and PMBoK 5 processes
in information systems project management. Computer Standards & Interfaces, 50, 216-
222.