MGT 323 Project Management
Case Study- Critical Thinking
Acme Corporation embarked upon an optimistic project to develop a new product for the marketplace. Acme’s scientific community made a technical breakthrough and now the project appears to be in the development stage, more than being pure or applied research. The product is considered to be high tech. If the product can be launched within the next four months, Acme expects to dominate the market for at least a year or so until the competition catches up. Marketing has stated that the product must sell for not more than $150–$160 per unit to be the cost-focused market leader. Acme uses a project management methodology for all multifunctional projects. The methodology has six life cycle phases:
● Preliminary planning
● Detailed planning
● Execution/design selection
● Prototyping
● Testing/buyoff
● Production
At the end of each life cycle phase a gate/phase review meeting is held with the project sponsor and other appropriate stakeholders. Gate review meetings are formal meetings. The company has demonstrated success following this methodology for managing projects. At the end of the second life cycle stage of this project, detailed planning, a meeting is held with just the project manager and the project sponsor. The purpose of the meeting is to review the detailed plan and identify any future problem areas that will require involvement by the project sponsor.
The Meeting
Sponsor: I simply do not understand this document you sent me entitled “Risk Management Plan.” All I see is a work breakdown structure with work packages at level 5 of the WBS accompanied by almost 100 risk events. Why am I looking at more than 100 risk events? Furthermore, they’re not categorized in any manner. Doesn’t our project management methodology provide any guidance on how to do this?
Project Manager: All of these risk events can and will impact the design of the final product. We must be sure we select the right design at the lowest risk. Unfortunately, our project management methodology does not include any provisions or guidance on how to develop a risk management plan. Perhaps it should.
Sponsor: I see no reason for an in-depth analysis of 100 or so risk events. That’s too many. Where are the probabilities and expected outcomes or damages?
Project Manager: My team will not be assigning probabilities or damages until we get closer to prototype development. Some of these risk events may go away altogether.
Sponsor: Why spend all this time and money on risk identification if the risks can go away next month? You’ve spent too much money doing this. If you spend the same amount of money on all of the risk management steps, then we’ll be way over budget.
Project Manager: We haven’t looked at the other risk management steps yet, but I believe all of the remaining steps will require less than 10 percent of the budget we used for risk identification. We’ll stay on budget.
1. Was the document given to the sponsor a risk management plan?
2. Did the project manager actually perform effective risk management?
3. Was the appropriate amount of time and money spent identifying the risk events?
4. Should one step be allowed to “dominate” the entire risk management process?
5. Are there any significant benefits to the amount of work already done for risk identification?
6. Should the 100 or so risk events identified have been categorized? If so, how?
7. Can probabilities of occurrence and expected outcomes (i.e., damage) be accurately assigned to 100 risk events?
8. Should a project management methodology provide guidance for the development of a risk management plan?
9. Given the life cycle phases in the case study, in which phase would it be appropriate to identify the risk management plan?
10. What are your feelings on the project manager’s comments that he must wait until the prototyping phase to assign probabilities and outcomes?

Leave a Reply