Quotes & Sayings About Project Risk Management

If you've been in the software business for any time at all, you
know that there are certain common problems that plague one
project after another. Missed schedules and creeping requirements
are not things that just happen to you once and then go
away, never to appear again. Rather, they are part of the territory.
We all know that. What's odd is that we don't plan our projects
as if we knew it. Instead, we plan as if our past problems are
locked in the past and will never rear their ugly heads again. Of
course, you know that isn't a reasonable expectation. — Tom DeMarco

Interestingly, Agile's scrum-team approach has its own way of aggregating some execution risk. For example, in a traditional "single task owner" approach, the risk of execution is not aggregated at all, leaving that task owner to add a lot of task-level buffer to self-insure and deliver on his commitment. In contrast, a 5-person scrum team aggregates the risk that any single individual will make slow progress, as the other four team members can often make up the deficit.

But why aggregate only up to the scrum-team level? Taking a lesson from the insurance industry, the more that risk can be aggregated, the easier it is to manage. Applied to projects, this will nearly always mean that it's better to aggregate risk at the project level. As a result, an Agile project can improve speed by avoiding sprint-level commitments. — Michael Hannan

1. Project What is the project? Why is it unique? Why is the business needed? Why will customers love your product? 2. Partners Who are you? Who are the partners? What are your educational backgrounds? How much experience do you all have? How are you and your partners qualified to make the project a success? 3. Financing What is the total cost of the project? How much debt and how much equity is there? Are partners investing their own money? What is the investor's return and reward for their risk? What are the tax consequences? Who is your CFO or accounting firm? Who is responsible for investor communications? What is the investor's exit? 4. Management Who is running your company? What is their experience? What is their track record? Have they ever failed? How does their experience relate to your industry? Do you believe this is the strongest management team you can assemble? Can you pitch them with confidence? — Donald J. Trump

One of the responsibilities faced by the Environmental Genome Project is to provide the science base upon which society can make better informed risk management decisions. — Samuel Wilson

I found the concept of hindsight bias fascinating, and incredibly important to management. One of the toughest problems a CEO faces is convincing managers that they should take on risky projects if the expected gains are high enough. Their managers worry, for good reason, that if the project works out badly, the manager who championed the project will be blamed whether or not the decision was a good one at the time. Hindsight bias greatly exacerbates this problem, because the CEO will wrongly think that whatever was the cause of the failure, it should have been anticipated in advance. And, with the benefit of hindsight, he always knew this project was a poor risk. What makes the bias particularly pernicious is that we all recognize this bias in others but not in ourselves. — Richard H. Thaler

A study of project and risk management in software projects in the public sector found that an informal partnership between the project's business owner and the project manager was seen by the latter as providing more effective project proprietorship and governance than the project steering committee [1]. This suggests that the application of governance may be more important than its form. This paper, however, focuses only on formal and explicit governance — Anonymous