Max Megahertz Project

Max Megahertz Project

THE CASE:
Olaf Gundersen, the CEO of Wireless Telecom Company, is in a quandary. Last year he accepted the Maximum Megahertz Project suggested by six up-and-coming young R&D corporate stars. Although Olaf did not truly understand the technical importance of the project, the creators of the project needed only $ 60,000, so it seemed like a good risk. Now the group is asking for $ 800,000 more and a six-month extension on a project that is already four months behind. However, the team feels confident they can turn things around. The project manager and project team feel that if they if they hand inn there a little longer they will be able to overcome the roadblocks they are encountering—especially those that with the project hint that the power pack problem might be solved, but “the battery problem will never be solved.” Olaf believes he is locked into this project; his gut feeling tells him the project will never materialize, and he should get out. John, his human resource manager, suggested bringing in a consultant to axe the project. Olaf is thinking maybe he should do that on this project if it needs to be terminated.
Olaf decided it call his friend Dawn O’Connor, the CEO of and accounting Software Company. He asked her “what do you do when project costs and deadlines escalate drastically?” Her response was, “Let another project tically? How do you handle doubtful project?” Her response was, “Let another project manager look at the project. Ask: ‘If you took over this project tomorrow, could you bring the project in on time and with the extended time and additional money?’ If the answer is no, I call my top management team together and have them review the doubtful project in relation to other project in relation to other projects in our project portfolio.” Olaf feels this is good advice.
Unfortunately, the Maximum Megahertz Project is not an isolated example. Over the last five years there have been three projects that were never completed. “We just seemed to pour more money into them, even though we had a pretty good idea the projects were dying. The cost of those projects was high; those resources could have been better used on other projects.” Olaf wonders, “Do we ever learn from our mistakes? How can we develop a process that catches errant projects early? More importantly, how do we ease a project manager and team off an errant project without embarrassment?” Olaf certainly does not want to lose the six bright stars on the Maximum Megahertz Project.
Olaf is contemplating how his growing telecommunications company should deal with the problem of identifying project that should be terminated early, how to allow good managers to make mistakes without public embarrassment, and how they all can learn from their mistakes.

REQUIREMENT:
You are to analyze the case and present a plan of action that attacks the problem. The action plan is to be a written report suitable for (Olaf) executive management review — about a page and a half prepared as a WORD Doc. .
After presenting the written plan of action, develop a WBS of your proposed plan. PRESENT THE WBS IN A GANTT CHART. The WBS is to contain at least 20 activities that represent your proposed action plan. Use MS Project or open Project to prepare the Gantt Chart.
You are not to develop an action plan to attack the technical problem at WTC. The issue at WTC appears to be a systemic problem related to selecting and managing projects.

Click Here For More Details on How to Work on this Paper…………..

Need a Professional Writer to Work on this Paper and Give you a 100 % Original Paper? Click Here and Get this Essay Done………………