Featured Post

Nutrition Facts Label Coursework Example | Topics and Well Written Essays - 250 words

Sustenance Facts Label - Coursework Example The ascent of science and food innovation have constrained numerous worldwide organizations i...

Sunday, March 22, 2020

Blue Spider Project Case Studies free essay sample

Gary Anderson failed to communicate effectively both internally and externally. Internally, Gary had been consistently not updating the status of the project or any decision made to other functional managers. For example, when Gary started testing the new material JXB-3, he didn’t notify the testing manager and as a result, work that was no longer required were done which not only increased the cost of the project but also made the testing manger being upset as he needed to play catch-up and reallocate his resource. Gary Anderson repeated the mistake of having poor communication with internal staff when he didn’t notify the production manager of the rescheduling of the verification mix and forced the production of the mix to be performed during overtime which again increased the cost of project and caused the production staff making a mistake in the mix. More importantly Gary failed to maintain a strong external communication with the customer right from the start of the project. We will write a custom essay sample on Blue Spider Project Case Studies or any similar topic specifically for you Do Not WasteYour Time HIRE WRITER Only 13.90 / page In the beginning of the project when Gary was ‘living’ in the research lab, it was basically impossible for the customer to contact Gary if they wanted an update of the project or had any questions. The customer didn’t have a clue of whether Park had started doing any work yet and they would be very concerned as Lord’s contract worth much more. Gary had broken the trust from Lord at the start of the project and as a result, Lord decided to demand more frequent communication from Gary which increased Gary’s work burden and the cost of the project. Once again Gary haven’t learnt his lesson on communication and done the same thing again when he didn’t informed Lord of using the new material – JXB-3 in the interchange meeting which Gary supposed to exchange information with the customer. This suddenly change of using the new material eventually upset Lord and the Army (The prime customer) and as a result Lord lost even more trust in Parks and Gary and required Gary to have weekly interchange meeting which led to even more work for Gary. Another aspect that increased the risk of the project was fact that Park wasn’t honest in the tender by not stating the fact that the design they had couldn’t meet the required specification, Park already considered forcing the customer to change the specification as the project progress. This meant even before the project started, Gary was faced with the problem of developing an alternative test matrix that would meet the specification requirement which involved many hours of additional work that wasn’t budgeted. Another issue was that Gary was provided the opportunity to be the project manager because of his strong technical Ramp;D background. He had no prior project management experience or skills to manage a project. Gary failed to become like an ‘outsider’ to maintain a proper balance between technical and administrative responsibility. In the beginning of the project, Gary still thought that he was an engineer and focused too much time on Ramp;D in the lab. This was due to the fact that Gary has too much pride in his technical skills and thought he was best engineer in the plant therefore he wasn’t willing to delegate the technical responsibly to the chief project engineer as he wanted to proof that he was more capable. Gary did no administrative work at all. He had other project office personnel running the weekly team meeting and presenting the administrative data. Those administrative tasks should be managed by Gary which will give the customer more confidence that the project manager was closely monitoring the progress of the project. Before the customer meeting, Gary didn’t send the agenda or any relevant hand-outs and as a result customer didn’t know what to expect in the meeting and also had no time to digest the technical data that was presented leading to customer dis-satisfaction. There were also no minute taken for all meetings meaning that anyone who were unable to attend the meeting were kept in the dark in regards to status of the project. Another factor that increased the risk of the project was that Henry Gable wasn’t a suitable sponsor of the project; Henry Gable had a high interest in the project as he could potentially receive bonus based on the performance of the project. He also didn’t fully trust Gary to run the project on his own and asked his engineer to frequently report the progress of the project to him. Henry Gable wasn’t supportive since the beginning of the project; Gary could never manage to get hold of him for meetings. In additional Henry Gable ntervened the project many times without consulting with Gary first. Without telling Gary, Henry Gable asked project team member to execute tasks that were not part of the program and charged it against Gary’s project. Examples were the testing the new material JXB-3 and the accelerated aging tests. As result, it made Gary harder to manage the project as he had to make last minute changes and account for unexpected cost. A major ris k that also caused problem in the project was the financial error that Gary made.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.