Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 4, Issue 16;   April 21, 2004: Scheduling as Risk Management

Scheduling as Risk Management

by

When we schedule a complex project, we balance logical order, resource constraints, and even politics. Here are some techniques for using scheduling to manage risk and reduce costs.
Two U.S. Army soldiers use binoculars and a riflescope to watch for insurgents

Two U.S. Army soldiers use binoculars and a riflescope to watch for insurgents downrange as they conduct a combat patrol near the Syrian border in Iraq on March 6, 2006. Patrol is a variant of "reconnaissance in force." Photo courtesy U.S. Department of Defense.

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 projects
Indeed. 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. Go to top Top  Next issue: Nonworkplace Politics  Next Issue

52 Tips for Leaders of Project-Oriented OrganizationsAre 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

Would you like to see your comments posted here? rbrenZLkFdSHmlHvCaSsuner@ChacbnsTPttsdDaRAswloCanyon.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.

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:

Bottle of poisonToxic Projects
A toxic project is one that harms its organization, its people or its customers. We often think of toxic projects as projects that fail, but even a "successful" project can hurt people or damage the organization — sometimes irreparably.
A white shark off the California coastNine Project Management Fallacies: IV
Some of what we "know" about managing projects just isn't so. Understanding these last three of the nine fallacies of project management helps reduce risk and enhances your ability to complete projects successfully.
My right foot. Arrow indicates the location of the break.My Right Foot
There's nothing like an injury or illness to teach you some life lessons. Here are some things I learned recently when I temporarily lost some of my independence.
The Marx brothers: Chico, Harpo, Groucho and ZeppoTINOs: Teams in Name Only
Perhaps the most significant difference between face-to-face teams and virtual or distributed teams is their potential to develop from workgroups into true teams — an area in which virtual or distributed teams are at a decided disadvantage. Often, virtual and distributed teams are teams in name only.
The Dalles of the St. Croix RiverThe Politics of the Critical Path: II
The Critical Path of a project is the sequence of dependent tasks that determine the earliest completion date of the effort. We don't usually consider tasks that are already complete, but they, too, can experience the unique politics of the critical path.

See also Project Management for more related articles.

Forthcoming issues of Point Lookout

Cracking walnuts with a nutcrackerComing February 1: The Big Power of Little Words
Big, fancy words, like commensurate or obfuscation, tend to be more noticed than the little everyday words, like yet or best. That might be why the little words can be so much more powerful, steering conversations where their users want them to go. Available here and by RSS on February 1.
Two bull elk sparring in Grand Teton National Park, WyomingAnd on February 8: Kerfuffles That Seem Like Something More
Much of what we regard as political conflict is a series of squabbles commonly called kerfuffles. They captivate us while they're underway, but after a month or two they're forgotten. Why do they happen? Why do they persist? Available here and by RSS on February 8.

Coaching services

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

Reprinting this article

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

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Twitter, or share a tweet Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy 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!
52 Tips for Leaders of Project-Oriented OrganizationsAre your project teams plagued by turnover, burnout, and high defect rates? Turn your culture around.
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.
Comprehensive collection of all e-books and e-bookletsSave a bundle and even more important save time! Order the Combo Package and download all ebooks and tips books at once.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!