I've always seen risk management as essential to project management, not a separate concept. It's a way to manage expectations. The same work and results will get you a very different outcome if you managed risk and expectations from the start.
Risk management is not project management
81–84 of 84 posts
Re: Risk management is not project management
#82I would argue that what the author describes is not risk management. It's a CYA game. Risk management is a part of project management. Real risk management identifies risk and defines mitigations to bring the risk down to an acceptable level. Passing the buck doesn't address the true risk; it only addresses the risk of who is accountable. Imagine a scenario where you need a new water heater in your home. One of the r…
Thanks for the feedback. I agree that risk management is a part of project management. What I, perhaps unclearly, was communicating is that people and organizations can often conflate the two. A project is not managed if all you've focused on are the risks. They are related, but distinct things. Let's take your example and apply it to my post. Imagine I need a new water heater. I found a contractor/company to come an…
Regarding the extension of the water heater example, I get what you're aiming at, but I'm not sure I agree. I deliberately used the term "licensed" because that is a risk management mechanism. Credentials and legal structures are a way we can manage risk. In this case, a license is a mechanism to ensure the work is insured in case it's done incorrectly. A bonded contract is another mechanism that mitigates the risk that the contractor won't complete the work. An inspector is a mechanism to manage the risk that the installation wasn't performed to code. None of these require me to know about mechanical systems, or hoop stress vs. longitudinal stress, or any other design elements. Now I agree on a simple example, this may be stretching the analogy. But when we get to really complex projects, I don't think it's entirely reasonable for a PM to be familiar with the aspects to that degree. Of course it's preferential, but on some projects I've been a part of, it's all but impossible for a PM to be knowledgable about control theory, and environmental compliance, and aerodynamics, and material science, and contract law etc. to a sufficient degree to manage the risk themselves. That's why they have systems engineers, codes, inspectors, and quality assurance plans, etc. These are the frameworks for risk management.
Re: Risk management is not project management
#83I've always seen risk management as essential to project management, not a separate concept. It's a way to manage expectations. The same work and results will get you a very different outcome if you managed risk and expectations from the start.
OP here. I think I did a poor job of communicating this exact point. I agree with you - risk management is a part of good project management. The point I was attempting to convey is when organizations consider projects (or project tasks) as managed when all they've done is shift risk without consideration of the ability to _actually_ accomplish said project/task. The myopic focus on risk can get in the way of _actual…
Re: Risk management is not project management
#84Earlier quoted context omitted.
I agree, but it's a hard balance to strike and depends on the writer's target audience. RACI is a pretty common acronym for anyone doing project management professionally. I'd not define REST, HTTP, etc; in an engineering doc.
How hard is it to use ?