"Taking an observation at the pole." The photo shows a member of the Amundsen expedition (probably Roald Amundsen himself) taking an observation to confirm his achieving the South Pole on December 14, 1911. Seen in the background is the line of the horizon. Most of the journey to the pole and back consisted of crossing a plateau and an ice sheet. Since both were (and are) essentially free of landmarks, navigation was a critical safety factor. To ensure his safe return, Amundsen marked his poleward path with snow cairns at three-mile intervals, each sturdily built and two meters high, one visible from the next. Each contained a record of its position, the distance to the last supply depot, and the bearing to the previous cairn. In this way, to reach the next depot on his return, he did not have to rely on the weather being clear enough for a sun sighting. In case somehow he missed his trail, he marked his depots with flags, across his path, spaced every half-mile, each flag numbered and bearing a record of the distance and bearing to the depot. His dogs also left behind a trail of spoor, which, being dark in color, stood out against the ice and snow, marking the trail for the return trip. All of these measures comprised Amundsen's approach to mitigating navigational risk on his return. They protected him against inability to sight the sun, against compass loss or failure, against whiteout, and against wind-driven erasure of his tracks. Moreover, these measures, taken together, were either noninteracting or only weakly interacting. It was a fiendishly clever design. Photo by Steve Nicklas, NOS, NGS. Courtesy U.S. National Oceanic and Atmospheric Administration. The photo originally appeared in The South Pole: an account of the Norwegian Antarctic expedition in the "Fram," 1910-12, by Roald Amundsen. Volume 2: p. 112.
In Part I of this two-part series, we examined the organizational and political risks of risk management plans and processes. Now we turn to the risks that arise from change and from the interactions between risks.
- Risk dynamics risk
- Risk is a dynamic attribute of projects. Even if a project were frozen in place, its risk probabilities and risk impacts could change, because its environment changes. It's necessary to review risk plans with a frequency compatible with the volatility of the risk environment, which is itself difficult to estimate.
- Indicators of risk dynamics risk include risk plans that remain unchanged for long periods of time; budgets and schedules that omit risk reviews or perhaps schedule them infrequently; and retrospectives that don't address risk review. If these indicators are present, risk dynamics risk is also likely present.
- Intra-project risk interactions
- Risk interactions within a given project are especially problematic. Two risks might seem independent, but the probability of one occurring might change if the other materializes; or the response to one risk might alter the consequences of or the probabilities of materialization of others; or the response to one risk might limit the project's ability to respond to another.
- For instance, if Arthur is backup for both Tory and Chris, all's well, as long as either Tory or Chris is available. If both become unavailable, we have trouble.
- The method known as morphological analysis developed by Fritz Zwicky, is useful for uncovering intra-project risk interactions. In this method, you examine all pairs of risks and ask, "If both risks materialize, will our planned responses still be effective?" If you find that the answer is "no," you can revise your plan. You can generalize this procedure to triples of risks, quadruples, and so on. For more on morphological analysis, see the article by Tom Ritchie at the Web site of the Swedish Morphological Society. Or take your pick from hundreds of sources.
- Inter-project risk interactions
- An inter-project risk interaction occurs when conditions in a given project change risk probabilities in another project, or cause risks to materialize in another project.
- For example, If Arthur is backup for both
Tory and Chris, all's well,
as long as either Tory or
Chris is availablesuppose two projects are scheduled to use the same resource serially. If the first project is delayed, the availability to the second project of that same resource changes. At the time of development of the risk plan of the second project, knowledge about the strategies and risks of the first would have been useful, but such information, sadly, is rarely shared. - To limit inter-project risk interaction risk, coordinate risk reviews with projects likely to transmit risk back and forth. If the risk profile of one of the projects changes, there is enhanced probability of impact on the other.
Most risk conditions are connected to at least a few other risk conditions, either internal or external to the project. Maps of these connections can be very helpful.
First issue in this series
Top
Next Issue
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. More info
Your comments are welcome
Would you like to see your comments posted here? rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend me your comments by email, or by Web form.About Point Lookout
Thank you for reading this article. I hope you enjoyed it and
found it useful, and that you'll consider recommending it to a friend.
This article in its entirety was written by a human being. No machine intelligence was involved in any way.
Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.
Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.
Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.
Related articles
More articles on Project Management:
Communication Traps for Virtual Teams: I- Virtual teams encounter difficulties that rarely confront face-to-face teams. What special challenges
do they face, and what can we do about them?
How to Make Good Guesses: Tactics- Making good guesses probably does take talent to be among the first rank of those who make guesses.
But being in the second rank is pretty good, too, and we can learn how to do that. Here are
some tactics for guessing.
Seven Planning Pitfalls: I- Whether in war or in projects, plans rarely work out as, umm well, as planned. In part, this is due
to our limited ability to foretell the future, or to know what we don't know. But some of the problem
arises from the way we think. And if we understand this we can make better plans.
Defect Streams and Their Sources- Regarding defects as elements of a stream provides a perspective that aids in identifying causes other
than negligence. Examples of root causes are unfunded mandates, misallocation of the cost of procedure
competence, and frequent changes in procedures.
Depth First or Breadth First?- When investigating candidate solutions to a problem, we tend to focus first on what we believe is the
"best bet." But a more systematic approach can sometimes yield dramatic advantages by reducing
the cost of the investigation and the time it requires.
See also Project Management for more related articles.
Forthcoming issues of Point Lookout
Coming October 1: On the Risks of Obscuring Ignorance- A common dilemma in knowledge-based organizations: ask for an explanation, or "fake it" until you can somehow figure it out. The choice between admitting your own ignorance or obscuring it can be a difficult one. It has consequences for both the choice-maker and the organization. Available here and by RSS on October 1.
And on October 8: Responding to Workplace Bullying- Effective responses to bullying sometimes include "pushback tactics" that can deter perpetrators from further bullying. Because perpetrators use some of these same tactics, some people have difficulty employing them. But the need is real. Pushing back works. Available here and by RSS on October 8.
Coaching services
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.
Get the ebook!
Past issues of Point Lookout are available in six ebooks:
- Get 2001-2 in Geese Don't Land on Twigs (PDF, )
- Get 2003-4 in Why Dogs Wag (PDF, )
- Get 2005-6 in Loopy Things We Do (PDF, )
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
- Get 2009-10 in The Questions Not Asked (PDF, )
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )
Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info
Follow Rick
Recommend this issue to a friend
Send an email message to a friend
rbrenaXXxGCwVgbgLZDuRner@ChacDjdMAATPdDNJnrSwoCanyon.comSend a message to Rick
A Tip A Day feed
Point Lookout weekly feed
My blog, Technical Debt for Policymakers, offers
resources, insights, and conversations of interest to policymakers who are concerned with managing
technical debt within their organizations. Get the millstone of technical debt off the neck of your
organization!
Is every other day a tense, anxious, angry misery as you watch people around you, who couldn't even think their way through a game of Jacks, win at workplace politics and steal the credit and glory for just about everyone's best work including yours? Read 303 Secrets of Workplace Politics, filled with tips and techniques for succeeding in workplace politics. 