Scheduling as Risk Management

Turning the car key in the door lock, Marian was relieved that they'd finally agreed to get out for lunch, because she wanted a change of scene for the conversation she and Kevin and James were about to have. The door locks all clicked open, and the three of them hopped in.

"Where to," she said.

Kevin answered from the back seat: "You have to ask?"

Marian looked up at Kevin in the rear-view mirror. "Just trying to give you an opportunity for input," she replied. At the end of the loop road, she turned left towards Mike's, where they always went for lunch when projects were in trouble.

James began immediately. "I wish we'd found out about the Georgetown products before we did the Pyramid modules — we wouldn't be here now. But how could we have known?"

Kevin, of course, had the answer. "They could've told us," he said dryly. Marian and James laughed weakly.

"Yeah, there is that," Marian said. "But they've done this to us before. You'd think we would have learned by now."

Projects are full
of surprises — that's
what makes
them projectsIndeed. Projects are full of surprises — that's what makes them projects. Still, we can reduce the incidence of surprises by cleverly sequencing the project's tasks. Here are some tips for using schedule to manage risk.

Avoid the logical-order trap

Some projects impose a logical order on task sequence. A building, for example, has to have its foundation in place before the first structural elements go up. But unless the laws of physics intervene, keep an open mind about the order of things.

Exploit leverage

Give preference to tasks that reduce costs, either because they spin off tools you can use, or because you can learn something valuable, or because they provide a morale boost.

Delay creating what you don't need

Building or designing something before it's needed creates constraints through commitment. Delaying preserves flexibility.

If you think something might be difficult, find out early

Schedule the solutions to unsolved problems so that bad news arrives early, when you have time to sort out alternate approaches, and before other elements impose constraints.

Use reconnaissance teams

Designate teams to perform reconnaissance in force, looking for traps before the main body of the project reaches them. Give these teams enough budget to run tests that reveal weaknesses before you've made major commitments.

Avoid resource optimization

Shortening the critical path by optimizing resource allocation is a risky strategy. Most development projects aren't predictable enough for this kind of fine-tuning.

Get comfortable with placeholders

We use placeholders when scheduling requires them, especially in the critical path. But building placeholders is a wonderful way to reconnoiter — to find out about trouble early. Use them more often.

You can do the same things when you read. Sometimes reading the end first gives you a useful mental framework for the beginning and middle. If you're doing that right now, I hope you enjoy reading the beginning and the middle of this article.  Top    Next Issue

Are your projects always (or almost always) late and over budget? Are your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around. Read 52 Tips for Leaders of Project-Oriented Organizations, filled with tips and techniques for organizational leaders. Order Now!

Your comments are welcome

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:

Dispersity Adversity

Geographically and culturally dispersed project teams are increasingly common, as we become more travel-averse and more bedazzled by communication technology. But people really do work better together face-to-face. Here are some tips for managing dispersed teams.

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?

Unresponsive Suppliers: II

When a project depends on external suppliers for some tasks and materials, supplier performance can affect our ability to meet deadlines. How can communication help us get what we need from unresponsive suppliers?

Cost Concerns: Comparisons

When we assess the costs of different options for solving a problem, we must take care not to commit a variety of errors in approach. These errors can lead to flawed decisions. One activity at risk for error is comparing the costs of two options.

Should We Do This?

Answering the question, "Should we do this?" is among the more difficult decisions organizational leaders must make. Weinberger's Six Tests provide a framework for making these decisions. Careful application of the framework can prevent disasters.

See also Project Management and Project Management for more related articles.

Forthcoming issues of Point Lookout

Coming May 14: Working with the Overconfident

A cognitive bias known as the Overconfidence Effect causes us to overestimate the reliability of our judgments. Decisions we make based on those judgments are therefore suspect. But there are steps we can take to make our confidence levels more realistic, and thus make our decisions more reliable. Available here and by RSS on May 14.

And on May 21: Mismanaging Project Managers

Most organizations hold project managers accountable for project performance. But they don't grant those project managers control of needed resources. Nor do they hold project sponsors or other senior managers accountable for the consequences of their actions when they interfere with project work. Here's a catalog of behaviors worth looking at. Available here and by RSS on May 21.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenDJpmhgyaDTwBQXkhner@ChacmGoYuzfZpOvDQdRkoCanyon.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