a Blog reader thinks that she has found a Bug when using Resource Pool, but it is not a Bug. I will show you a case in MS PROJECT 2013!
First, as usual I will make a Resource Pool and I will save it:
I will save the Resource Pool:
No I will create my first Project with two Tasks and I will assign Resources from the Resource Pool:
I will repeat those steps above for my Second Project, and I’ll get:
John and Mary are Over-allocated, as expected. Now suppose, that you find out, that you will not work on Second Project, because it is Canceled (for any reason). What Will you do? Will you simply delete Second Project file? NO! Why? Look what will happen.
I have those mpp Files:
After I erase Project2 mpp file I’ll get:
I’m going to open Project1, and I’ll get:
As you can see, John and Mary are still Over-allocated. But, how can it be? Let’s look at the Resource pool Resource Usage View:
You can see that even Project2 does not exists any more, Resource pool has still data (Task) from it. So before erasing project file, first remove allocation, like this:
then save this Project file along with Resource pool file,m and THEN Erase it! you will get:
Again Resource Usage View in Resource Pool:
Task are still here, but they are not assigned to anyone. Still not happy with that. Than in Project2 erase all Tasks, then save it along with Resource Pool, and then erase it.
Simple, but you must be very careful!