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.
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 welcomeWould you like to see your comments posted here? rbrenXOBvoCIAiBRxGdGlner@ChacSCrfdVXsNLiIXrjooCanyon.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.
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.
More articles on Project Management:
- 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.
- Remote Facilitation in Synchronous Contexts: II
- Facilitators of synchronous distributed meetings — meetings that occur in real time, via telephone
or video — encounter problems that facilitators of face-to-face meetings do not. Here's Part II
of a little catalog of those problems, and some suggestions for addressing them.
- Managing Risk Revision
- Prudent risk management begins by accepting the possibility that unpleasant events might actually happen.
But when organizations try to achieve goals that are a bit out of reach, they're often tempted to stretch
resources by revising or denying risks. Here's a tactic for managing risk revision.
- Unnecessary Boring Work: I
- Work can be boring. Some of us must endure the occasional boring task, but for many, everything about
work is boring. It doesn't have to be this way.
- Yet More Obstacles to Finding the Reasons Why
- Part III of our catalog of obstacles encountered in retrospectives, when we try to uncover why we succeeded
— or failed.
Forthcoming issues of Point Lookout
- Coming November 22: Motivation and the Reification Error
- We commit the reification error when we assume, incorrectly, that we can treat abstract constructs as if they were real objects. It's a common error when we try to motivate people. Available here and by RSS on November 22.
- And on November 29: Manipulators Beware
- When manipulators try to manipulate others, they're attempting to unscrupulously influence their targets to decide or act in some way the manipulators prefer. But some targets manage to outwit their manipulators. Available here and by RSS on November 29.
I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenFVAhgBzAzNBNJTdzner@ChacNnFtgCOEeqzUYDAyoCanyon.com or (617) 491-6289, 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, USD 11.95)
- Get 2003-4 in Why Dogs Wag (PDF, USD 11.95)
- Get 2005-6 in Loopy Things We Do (PDF, USD 11.95)
- Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, USD 11.95)
- Get 2009-10 in The Questions Not Asked (PDF, USD 11.95)
- Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, USD 28.99)
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
- Ten Project Management Fallacies: The Power of Avoiding Hazards
- Most of what we know about managing projects is useful and effective, but some of what we know "just ain't so." Identifying the fallacies of project management reduces risk and enhances your ability to complete projects successfully. Even more important, avoiding these traps can demonstrate the value and power of the project management profession in general, and your personal capabilities in particular. In this program we describe ten of these beliefs. There are almost certainly many more, but these ten are a good start. We'll explore the situations where these fallacies are most likely to expose projects to risk, and suggest techniques for avoiding them. Read more about this program. Here's a date for this program:
- 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.