🎬 [VIDEO] Top 3 Reasons for Resource Pools

[CynthiaBoon]

Your “On-Demand Workfront CSM” is back with a new Top 3 video! This time we’re talking about Resource Pools, and some creative ways to use them.  This topic always inspires discussion, so check out the video below. 

Just getting started with Resource Pools? First things first, what are they? 

• A Resource Pool is a collection of users that are needed at the same time for the completion of a project. 
• A Resource Pool can be shared across multiple projects, programs, or portfolios when it is associated with all the projects in the programs and portfolios. 
• After you populate your Resource Pools with users, you can associate them with projects and templates, and you can associate as many Resource Pools as needed with a project, template, or user. 
• For more info, check out the Resource pools overview article. 

There are several genius-level examples of why the Experience League Workfront Community is so amazing and this topic is no exception.  Just another plug to post your questions or start a discussion when something doesn’t seem right, and help will be on the way. 

• Resource Pool – Experience League Community Discussion 

As I mentioned in the video, Resource Management tools can take a village, so here’s my Oscar speech thanking all the folks that inspired this video. Special thanks to @MelanieM1, @Doug_Den_Hoed__AtAppStore, @skyehansen, @Madalyn_Destafney, @Lyndsy-Denk, and @KellieGWAB for the discussions and @RandyRoberts  for tagging me. Also, thanks to @Ross_Barton for bringing the topic back on the radar, and @CorinnaJ  for being the coolest person (in general) and, of course sharing her Resource Management brain with me!  

[Doug_Den_Hoed__AtAppStore]

Mmmmm...resourcing. Delicious! Thanks @CynthiaBoon!

Ever the contrarian, I'll kick things off. In contrast to my Right Answer on the related thread above (assuming that isn't overturned upon appeal, citing this post), I do not use Resource Pools personally, for several reasons:

• managing skills (via roles with % per role per person) is more granular and practical
• over time, such organizational constructs invariably change (see "reorg" for more information), causing dissonance and confusion between the Old Way and the New Way, and (eventually) extra work to "catch up" the former to the latter...assuming there hasn't been another New New Way in the meantime
• in contrast.."One word: Assignments" which in my opinion and experience are a far superior means of conceptualizing, discussing, filtering, and managing Resources within Workfront...so much so, in fact, that it lead to the creation (with our like-minded clients' insights) of our Capacity Charts solution, which I'd be happy to chat about via doug.denhoed@atappstore.com, or perhaps present sometime to those on this thread interested in learning more

I look forward to additional conversation here as it unfolds.

Regards,

Doug

[Lyndsy-Denk]

Thank you, @CynthiaBoon, for trying to address this.

Two things:

1. I've only heard reasons why resource pools can be helpful; not why they're required. If we don't use Resource Pools, does Planner not fully function?
2. What if we don't yet know what the resource pools should be for projects? In my organization's case, we're trying to assess our capacity at a more general level. One of the questions we're trying to answer during our exercise is, "Which resource pools should we use?" Are we putting the cart before the horse? If so, how do we do capacity planning on all projects, even the ones without resource pools?

Maybe that's where @Doug_Den_Hoed__AtAppStore comes in?

[CorinnaJ]

Hi @Lyndsy-Denk - let me see if I can answer your questions.  

1. Yes, you do need to use Resource Pools to have accurate data in the Resource Planner.  I think there are several reasons Resource Pools are required but probably the most important is that they cordon off resources so that a particular role or resource that your team is using is not counted as a resource for another team or group or vice versa.  Resource Pools are a really easy way to show the resources your team or department actually has access to and connect those resources to the projects they are or will be working on.
2. I think it's always crucial to think through Resource Pools and Job Roles.  Please note that you can have more than one Resource Pool attached to a project and similarly, users can be in more than one Resource Pool.  I think the important question to ask is, "What is the RM data you or your leadership wants to see?"  That should inform how you structure your Resource Pools.  

[Doug_Den_Hoed__AtAppStore]

Hi @Lyndsy-Denk,

Yes, exactly: although in the long run some overlap does tend to occur, we design our solutions to compliment Workfront's built in As Designed features. In the case of our Capacity Charts solution, all you need in order to get going is a minimal set of Workfront information:

• Users
• Schedules
• Roles
• Tasks
• (Optional) Personal Time Off

With those in place, our Capacity Charts can help you visualize your mid and long term staffing needs against real projects and make decisions such as (e.g. for crunch times) whether to hire extra skills or defer projects to allow some breathing room. As you get control of your data and plans, you can also introduce Workload Balancer and/or the Resource Planner in parallel, using those features where they fit best with your processes. Happy to chat further at doug.denhoed@atappstore.com

Regards,

Doug

[Madalyn_Destafney]

I'm still trying to see the light with resource pools as opposed to just using Teams or Groups. I get now that you need them to utilize the Planner. When you associate a project with pool(s), how does that show what % of the project they are involved in? If you have a project with 10 tasks for example, and only 1 task touches a certain pool, how does WF see this? I guess confused about attaching pools to a project instead of only the tasks within it that need resources from the pool, ya know?

[CynthiaBoon]

So, I will always have to defer to Corinna on anything Resource Management, so feel free to take anything that I add with a grain of salt.  In terms of the Planner, my understanding is that in order to budget any of the Planned Hours or assignments, the Resource Pool has to be assigned at the Project level.  Meaning that without this, those Projects (and ultimately those hours/assignments), just "don't exist" as far as the Planner is concerned.  And to muddy the waters a bit more, from what I understand, if you're trying to budget for specific users, that user must be associated to a Job Role that is also included in the Resource Pool that is associated with the applicable project.

So the closest answer I could ever give for why Resource Pools, is mainly so that the Projects (along with any hours associated with those users and job roles) display in the Planner and can be budgeted. I found this list of prerequisites that shows what won't happen if they aren't assigned.  Posting it, just in case it could be helpful to anyone.  (It was news to me!)

Resource Planner - User Prerequisites

But here's the thing - I totally get what you're saying.  It makes more sense to me to assign the Resource Pools to the specific Tasks that are critical to completing the project.  (And maybe that was what Scenario Planner was supposed to solve towards back in the day?) The challenge for me was that the key factor for implementing Resource Management (being able to decline/"prioritize" work) wasn't ever really possible.  I did try to anticipate resource needs a quarter or two ahead of time, but mostly that was handled via our Governance process.  We mainly lived in the day-to-day of swapping out or moving around work as the priorities changed each week.  So a very light "Workload Balancing" was as close as I could get to RM.  I have heard that there are enhancements in the wind for this feature Roadmap, so I'm hoping we hear something soon.  (Keeping my fingers crossed for the Roadmap session on May 8th, but we'll see!)

[Doug_Den_Hoed__AtAppStore]

Thanks for the link @CynthiaBoon,

I concur with your "specific Tasks" world view, which is one reason our solutions use Assignments (whether role, or user) rather than Resource Pools.

Regards,

Doug