Techniques

Risk Happens

by Josh

Risk Happens

Guest post by Mike Clayton

Why Every Project Manager needs to Understand Risk

Project management is a discipline born from necessity.  If projects were not so challenging, we wouldn’t need a separate toolkit and processes.  But we do need them, because when we try to create change under constraints like schedule, performance and budget, we face the unknown.

Your response as a project manager is to define and plan your project with care, gathering all available data and then applying your experience, expertise and reasoning to generate a plan.

Planning Fallacy

Daniel Kahneman and Amos Tversky described “planning fallacy” as the consistent belief that you can deliver to a schedule – even when you have a track record of over-runs.  Believing your plan is an error almost as serious as failing to make one in the first place.

“Plans are worthless, but planning is everything”
President Eisenhower

Shift happens! Things go wrong.  The universe is no respecter of your plans.

Risk Management


So a second discipline – deeply intertwined with project management – is born of the same necessity: Risk Management.  A risk can be defined as:

“uncertainty that can affect outcomes”

Notice how this definition contains the two principal components of risk: uncertainty, which is measured by likelihood, and impact, which can be measured in many ways: financial, schedule, reputational, or the level of disruption to your project, for example.  Uncertainty arises for many reasons.  Here are seven of the most common:

  1. Projects are one-off endeavours, creating new products, services, assets or processes.  There is no specific history or experience to call upon when you are planning.
  2. Planning assumptions can be flawed due to lack of information or data, or incorrect information or data, or faulty interpretation of the information or data you have.
  3. You may miss something important in your planning, which you either failed to identify, identified but missed the significance, or could never reasonably have known it.
  4. Someone intervenes in an unexpected manner – unexpected because either your analysis of your stakeholders missed what should have been predictable, or because sometimes people act in an unpredictable manner.
  5. A genuinely unexpected – possibly even unforeseeable – event occurs.  If it was really unforeseeable, it is often referred to as a “black swan” event.
  6. A predictable event occurs, but its predictability extends to insufficient precision, rendering planning impossible.  Extreme weather and natural events are in this category: we know earthquakes happen in certain places, but cannot yet anticipate precisely where and when, and to what extent.
  7. Plain old human error – someone makes a mistake.

For all of these reasons, Project Management students need to make a careful study of risk management, and learn to feel comfortable with uncertainty.  You need to be able to identify, analyse and plan for risk.

This is why I wrote Risk Happens! Managing Risk and Avoiding Failure in Business Projects”.  It is written with new and less experienced project managers in mind, but I believe that there is plenty of material that experienced professionals will find useful and thought-provoking.  You can find out more at http://riskhappens.co.uk.

Win a Copy of Risk Happens!

My particular focus in training project managers has always been on practical tools and techniques.  I have carried this attitude into Risk Happens!  I am interested in what you think are the best – and most innovative – risk management tools and techniques.  Contribute your ideas at the end of the post and Josh and I will award the best response with a complimentary copy of Risk Happens!

You have until October 31, 2011 to win so leave a comment now!

{ 9 comments }

Rolling Wave Planning and Progressive Elaboration - photo via Flickr by Captain Kimo - Catching Up!

Hi Josh,

I am reviewing the PM PrepCast for the second time. I am scheduled to take the exam [soon].

Right now I have an issue discerning the difference between Rolling Wave Planning and Progressive Elaboration. Not that this issue by itself is pass/fail but every question answered correctly helps. Can you provide a some definitions that might be able to clear this up? The PMBOK guide definitions are not helping.

An excellent question!

Rolling Wave Planning

Rolling wave planning is a type of progressive elaboration. So if I put it in a list with other examples:

Progressive Elaboration (examples)

  • Rolling wave planning (usually this term is used in a waterfall project environment)
  • Sprint planning (Agile)
  • Kanban task decomposition (start with larger deliverables or feature sets, decompose into smaller pieces as they exit the backlog and go into the active value stream)
  • Prototyping

Progressive Elaboration

Progressive Elaboration just means you keep things months out at a high level and don’t try to guess what the details will be yet. Scope is broadly defined, specific tasks are probably not yet defined, and estimates are ROM (Rough Order of Magnitude).

As you get closer in time, you go through a re-planning effort to break down that vague, high-level plan down into specific sub-deliverables, tasks, and updated estimates that you can actually go and have your teams execute on.

Planning Packages

In my organization, we use a concept called planning packages when work is too far out in the future and too undefined. There are ROM estimates attached to these planning packages and we know in general what they are about. We can even define the deliverables associated with a planning package, although when we get closer those deliverables may be implemented differently than what was initially guessed at.

Will you leave a comment below with questions or to chip in your own $0.02 ?

{ 0 comments }

What Is A WBS?

Thumbnail image for What Is A WBS? by Josh July 7, 2011 Definitions

Great question from Bill today about what a WBS is and how it’s used in planning project scope: Hello Josh Please clarify something for me. I am only into chapter 7 of WBS Coach so if it is explained later please forgive me. From what I have read so far it seems that the WBS [...]

Click to continue…

Jenga Project Management Processes

Thumbnail image for Jenga Project Management Processes by Josh May 11, 2011 PPM/PMO

Project Managers can get a little nuts about process sometimes. I mean, really.  Really crazy.  We add, and add, and add.  It feels good, I think it’s an addiction actually. But then we end up with a pile of (insert expletive) that looks like a Jenga game about to fall over. We have to police ourselves. [...]

Click to continue…

Small Projects: How To Rock Them

Thumbnail image for Small Projects: How To Rock Them by Josh April 21, 2011 Cost

Feeling like your small projects aren’t giving you the experience you need?  I know where you’re coming from. It’s how “accidental” project managers like us start out.  Small businesses, small projects, small teams. I’ve worked in environments like this in the past, and currently volunteer for several non-profits where this is the case.  My activities with [...]

Click to continue…

Your Customers Don’t Care

Thumbnail image for Your Customers Don’t Care by Josh April 5, 2011 Leadership

I was in a local cafe the other day working on a Kanban training course I’ll be making available sometime soon. I grabbed the usual coffee for fuel and then a sugar avalanche of a toffee bar caught my eye. And I bought it. Because I have no impulse control whatsoever. I chewed the first [...]

Click to continue…