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.

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:

Some Causes of Scope Creep

When we suddenly realize that our project's scope has expanded far beyond its initial boundaries — when we have that how-did-we-ever-get-here feeling — we're experiencing the downside of scope creep. Preventing scope creep starts with understanding how it happens.

The Weaver's Pathway

When projects near completion, we sometimes have difficulty letting go. We want what we've made to be perfect, sometimes beyond the real needs of customers. Comfort with imperfection can help us meet budget and schedule targets.

Resuming Projects: Team Morale

Sometimes we cancel a project because of budgetary constraints. We reallocate its resources and scatter its people, and we tell ourselves that the project is on hold. But resuming is often riskier, more difficult and more expensive than we hoped. Here are some reasons why.

Risk Management Risk: I

Risk Management Risk is the risk that a particular risk management plan is deficient. It's often overlooked, and therefore often unmitigated. We can reduce this risk by applying some simple procedures.

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.

See also Project Management and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming September 25: Planning Disappointments

When we plan projects, we make estimates of total costs and expected delivery dates. Often these estimates are so wrong — in the wrong direction — that we might as well be planning disappointments. Why is this? Available here and by RSS on September 25.

And on October 2: Start Anywhere

Group problem-solving sessions sometimes focus on where to begin, even when what we know about the problem is insufficient for making such decisions. In some cases, preliminary exploration of almost any aspect of the problem can be more helpful than debating what to explore. Available here and by RSS on October 2.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenmhXARWRMUvVyOdHlner@ChacxgDmtwOKrxnripPCoCanyon.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 words in your inbox in one hour. License any article from this Web site. More info

Public seminars

The Race to the South Pole: Lessons in Leadership

On 14 December 1911, four men led by Roald Amundsen reached the South Pole. Thirty-five days later, Robert F. Scott and four others followed. Amundsen had won the race to the pole. Amundsen's party returned to base on 26 January 1912. Scott's party perished. As historical drama, why this happened is interesting enough. But to organizational leaders, business analysts, project sponsors, and project managers, the story is fascinating. We'll use the history of this event to explore lessons in leadership and its application to organizational efforts. A fascinating and refreshing look at leadership from the vantage point of history. Read more about this program.

Here's a date for this program:

• Baldwin-Wallace University, 275 Eastland Road, Berea, Ohio 44017: November 7, Kerzner Lecture Series/International Project Management Day, sponsored by Baldwin Wallace University and the Northeast Ohio Chapter of the Project Management Institute. Register now.
   

The Power Affect: How We Express Our Personal Power

Many people who possess real organizational power have a characteristic demeanor. It's the way they project their presence. I call this the power affect. Some people — call them power pretenders — adopt the power affect well before they attain significant organizational power. Unfortunately for their colleagues, and for their organizations, power pretenders can attain organizational power out of proportion to their merit or abilities. Understanding the power affect is therefore important for anyone who aims to attain power, or anyone who works with power pretenders. Read more about this program.

• A recording of a program presented June 29, 2017, Monthly Webinar, sponsored by Technobility Webinar Series. PMI members can earn 1.0 Category 'A' PDU by viewing this program. View this program now.