Hi Vazgen, For us it's probably a step back from resource pools. We don't do resource budgeting (yet) because we don't really see how it adds value in the workflow between planning tasks and assigning resources. i.e. For us if something is budgeted then it should become available for assigning resources. Without this workflow we don't really see the ROI in going through the budgeting process (though maybe it is a lack of understanding?). So at the moment, without using the resource planner for budgeting, the only benefit of setting up and assigning resource pools to projects is to be able to reduce the set of projects which you see in the planner (if you're using Project view). If you're using User view then the resource pools don't seem to do much that you can't do by using Teams in the filter. So overall we don't see much value in resource pools, but if changes were made to the effect of budgeting so that we wanted to do it, then we may well use resource pools.
Regards, David Cornwell