Home › Forums › Discussion › Managing resources in a matrixed organization for future projects › Reply To: Managing resources in a matrixed organization for future projects
Earl, sorry for the misinterpretation but that helps a lot. From what you provided I still believe that the baseline is your best option. You may want to create a single task at the front of your project to house the initial resource assignments. Assign the generic, role based resources and then baseline your project. That identifies the dates and expected utilization for each resource type. You can then zero out the work for this task/those resources and begin scheduling your project. You can also create a resource custom field for role to identify and map your generic and named resources together. That’s one option but from your initial requirements seems like a good option.
Now expanding that to your portfolio depends a lot on the number of projects, but here you go. Create a shared resource pool and assign resources to projects using that shared resource pool. That allows you to share resource demand across multiple projects. Details are too complex for a forum question but there are lots of blogs and articles that show you how and identify the considerations.
Last note, as you get more than 10-15+ project or 25-30+ resources it can become quite a challenge pretty quickly. It can also introduce corruption if not done correctly. At some point it becomes a job for Project Online/Server. Hope that helps…