Deep Dive into Microsoft Project Resource Pools: 5 Gotchas

In this article about resource pools, you’ll learn about a potential danger while swimming around in resource pools and hear about all the known gotchas I have run across in my dealings with resource pools.

An Important Note on Pool Safety and Security

Pool safety and security is important. After all, you’re sharing data with everybody who has access to the resource pool (via a linked project file). The concern that comes up the most is resource rates. Does John Doe need to know how much Jane Jill makes per hour? Will Jane get miffed when she finds out John is paid more for the same work? You betchya!

Unfortunately, Microsoft has never provided a solution for Microsoft Project Standard or Professional users. And since the cost of resources drives Project financial calculations, you really need to have something in that Rate column. Many of us resource “pool divers” have complained about this for years. (See this support blog post for an example of that.)

The easiest solution to this conundrum is to use blended rates for all resources when the rate is sensitive. In other words, don’t use the actual rate, but rather an average for a particular resource.

Say, for example that a support staff manager makes $200 per hour, and the lowest paid support staff makes $75 per hour. The blended rate for any instance of using a support staff resource is then $137.50, and that rate is used for all tasks assigned to any support staff entry in the resource pool. You might want to make a note of that in the resource pool itself, as this transparent strategy may appease any hate coming your way from HR.

If super precise calculations are needed (and blended rates won’t do), you’ll have to hire a smart VBA programmer to help you come up with a solution. (Feel free to contact me below, as I know a few of those.)

Part 1 of this deep dive teaches the theory and usefulness of Microsoft Project resource pools.

Resource Pool Gotchas

The following is a short list of potential confusions, frustrations and overall crazy things that I have encountered when using resource pools. Feel free to add to the list in the comment section below — I’m sure there are more!

Confusion

When opening a resource pool in use, you’re presented with a cryptic dialog box with unfamiliar language. There’s no help for this box to speak of, so taking my recommendation (or one from others) is your best bet. The issue comes up because two or more people are not allowed to edit the pool at the same time (which would be crazy). So changes made to project resources when the resource pool is locked remain local to the project until both the project file and the resource pool are opened in read-write mode. Then the files are synced and the change is propagated.

A recommendation: On opening a resource pool in use, you will see this:

I always use the middle click if I need to have the pool open and when I’m doing any pool maintenance. Once created, most activity is coming in from the project files, so maintenance should rarely be needed once the pool is up and running. But if you need to change a name’s spelling or rate for all projects, use the middle path.

More Confusion

When opening a project file, you are again presented with a cryptic dialog box, asking you to open the pool (it will then present a read-only copy for your reference) or skip it.

All you must be aware of is that permanent changes aren’t made to the resource pool until both the project files and resource pool are opened at the same time, with the resource pool opened in read-write mode. See the first confusion above and follow the middle click.

A recommendation: When you see this screen, just click OK. Then you’ll see a copy of the resource pool with all the changes (pending or otherwise). If you prefer not to see this shadow copy of the resource pool, select Do not open other files.

Strangeness

If you see file paths instead of, say, a file name inside your resource pool, for example, with the Project field, don’t be alarmed:

A recommendation: That just means that the projects aren’t opened, which for some strange reason they must be. Here is what the pool looks like when the projects are open and all is good:

Broken Links and File Management Snafus

Just like using Master Plan and Subplans in Project, you need to pay attention to file locations to avoid broken links. Once a project file is linked to a resource pool file, moving or renaming the pool file will break the link and wreak havoc. Fortunately, you’re warned:

A recommendation: I advise a sensible file management strategy where a file/folder hierarchy is created and maintained and where resource pools are stored one level above folders that contain project folders. I also suggest never changing the name of the resource pool file.

In addition, never create a resource pool by copying another one (and then replacing the resources with new ones). Hidden gremlins may exist in a pool file created this way.

Currency Confusion

Projects linked to a resource pool should all be using the same currency. If you try to link a file whose currency differs from the pool’s base currency, you’ll be warned:

While Project allows you to have resources with different currency rates, costs calculations will go haywire and reporting will be a problem.

A recommendation: For projects using a resource pool, just make sure all files are working with the same currency.

This concludes our deep dive into resource pools. Have you figured out something about resource pools that is worth sharing? Make sure to include it in the comments below. Last one in is a rotten egg!

Part 1 of this deep dive teaches the theory and usefulness of Microsoft Project resource pools.
Part 2 offers a step-by-step tutorial with a real-life example.
Part 3 offers an important security consideration and shares the most common gotchas.

Image Source