Guidelines for Sharing "Resources"

First things first: when referring to people in the abstract, I prefer words like "someone," "person," or "people." I dislike the word "resources," which, to me, evokes things like equipment, timber, and coalmines. OK. That's out of the way.

When team members have responsibilities to multiple teams, those teams all face risks. The unexpected happens. Priorities change. Schedules change. Time commitments cannot always be honored. We might try to schedule our efforts, but when team members belong to multiple teams, the plan and the reality are sometimes wildly different, even if the root cause of the trouble is elsewhere.

Here are four guidelines for sharing people more effectively than we often do.

Front-load the activities of shared people

Trouble sometimes arises in partner efforts. If resolving that trouble requires additional time from someone you share, you could lose access to that person. Moreover, even if the partner project goes smoothly, difficulties in other projects could result in schedule changes for the partner project, and the shared person might not be available at the time you scheduled.

If possible, schedule your own efforts so that the work that shared people do happens early.

Adjust effort estimates for interruption of flow

During planning, when we estimate effort, we often assume that the person doing the work is doing nothing else. Since that assumption is invalid for people with divided responsibilities, and since juggling multiple assignments does have associated costs, our estimates tend to be lower than the actual time required.

Make estimates that realistically account for the loss of time due to multiple assignments. When tracking actual effort data, track assignment multiplicity, too.

Combine hours into the longest possible contiguous bursts

To minimize Combine hours into the longest
possible contiguous burstslosses due to interruption of flow in the context of split assignments, combine hours of effort for each person into the largest possible contiguous chunks. Instead of one day per week for six weeks, schedule two days per week for three weeks, or four days in one week, and two days three weeks later.

You might have to negotiate with partner team leads, but when they understand the advantages of contiguous bursts, the negotiations are likely to be smooth.

Avoid the "MS Project flat rate syndrome"

Planners tend to use as weekly effort estimates for each person, the total estimated effort for each person divided by the task duration in weeks. Rarely does work actually proceed in this way. Even if it did, such a pattern maximizes the losses due to multiple assignments, because it maximally interrupts flow.

Actual work is usually performed in bursts. Use your project planning software to schedule those bursts.

People with multiple assignments are usually less effective than they would be if they had only one assignment. And they might be called away at any time. Plan for it.  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:

Scheduling as Risk Management

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.

Project Improvisation Fundamentals

Project plans are useful — to a point. Every plan I've ever seen eventually has problems when it contacts reality. At that point, we replan or improvise. But improvisation is an art form. Here's Part I of a set of tips for mastering project improvisation.

Ground Level Sources of Scope Creep

We usually think of scope creep as having been induced by managerial decisions. And most often, it probably is. But most project team members — and others as well — can contribute to the problem.

Managing Wishful Thinking Risk

When things go wrong, and we look back at how we got there, we must sometimes admit to wishful thinking. Here's a framework for managing the risk of wishful thinking.

On Anticipating Consequences

Much of what goes wrong when we change systems to improve them falls into a category we call unanticipated consequences. Even when we lack models that can project these results accurately, morphological analysis can help us avoid much misery.

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

Forthcoming issues of Point Lookout

Coming December 11: White Water Rafting as a Metaphor for Group Development

Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups. Available here and by RSS on December 11.

And on December 18: Subgrouping and Conway's Law

When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks. Available here and by RSS on December 18.

Coaching services

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