Project Management

Please login or join to subscribe to this thread

Professional and Social Responsibility

linkedin twitter facebook  
avatar
Muhammad Akbar Program Manager| Lantern Systems Riyadh, Riyadh, Saudi Arabia
You are responsible for developing high-level risks, assumptions, and constraints for your project. You meet with experts in your organization and document various risks in the project. However, in reviewing historical data from a previous project, you notice a significant additional risk to your project, one that no one else is aware of. What should you do to continue the project?
A.Do not document the risk since it is based on past data
B.Document it but make it a low-level risk
C.Document it and make it a high-level risk
D.Do not document the risk since nobody knows about i
Sort By:
avatar
Kamrul Chowdhury Manager, IT Application Support| Public Storage Los Angeles, California, United States
C.Document it and make it a high-level risk

?
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
It is a significant additional risk so common sense says that it should be evaluated using qualitative and quantitative risk analysis if neccessary, documentED as high or low level risk based on the evaluation. Since you mentioned it is a significant additional risk to the project then the answer which makes the most sense is C.
avatar
Tamer Zeyad Sadiq Assistant Cost Manager| Turner & Townsend Riyadh, Ar Riyad, Saudi Arabia
I think we should update to risk register first then make qualitative and quantitative analysis!!! for this case is C
avatar
Muhammad Akbar Program Manager| Lantern Systems Riyadh, Riyadh, Saudi Arabia
C - As a project manager, you have a responsibility to disclose accurate information to all project stakeholders honestly. Project managers must not disseminate false or misleading information. Thus, you must document it as a high-level risk. Even though the risk is based on past data, it must be documented because the risks could also be identified from the past data. Documenting it as a low-level risk would be a misleading act, and a project manager must not do that
avatar
Kevin Coleman Subject Matter Expert, Author, Speaker and Strategic Advisor| - Insights Pa, United States
All professionals should give back to their professions on a regular basis
avatar
Muthukrishnan Ramakrishnan Automation & Validation Engineer| Automation & Validation Solutions Taichung, Taichung, Taiwan
B should be the best option. As it is taken from old project, and all circumstances were different
avatar
James Lovell Project Manager| Mercy Technology Services Ballwin, Mo, United States
I'd have to go with another option- add it to the risk log but wait until the next risk management meeting with the project team before you evaluate the potential that it will occur, the risk impact etc. Let the experts weigh in on it.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Smoking is one of the leading causes of statistics."

- Fletcher Knebel

ADVERTISEMENT

Sponsors