I started writing about the mechanics of the portfolio analysis module of Microsoft Project Server back in 2010-2011 with Microsoft Project Server 2010. That resulted in this somewhat comprehensive (at the time) white paper that’s probably due for a couple of minor updates.
Over the last several years, I’ve made a couple of attempts to correct some of the errata and omissions in the paper as well as bring it into line with Project Server 2013 and the Project Online cloud based release. That has resulted in the following posts (organized in chronological order):
- Original white paper (See errata in the comments)
- Generic Resources and Portfolio Analysis
- Resource Plans and Portfolio Analysis (Note: As of writing, Resource Plans are effectively retired in the Online version of the product)
- Prioritization with Custom Fields
And now this. In this episode, I want to get you caught up on how Resource Engagements impact the resource analysis functionality in the Portfolio Analysis module. Turns out, this is quite easy. You’ll note in tenants with the features activated, you will now see this option in the setup screen:
So as you can see, you have the option of selecting whether resource engagements decrement from available capacity. One important thing to note is that if I have assignments that don’t map to an approved engagement – those assignments may not be part of the portfolio analysis if the second option is not selected.
Hence, if you want portfolio analysis to work the way it “used to” work, you would probably want to select the second option, i.e. don’t require resource managers to approve work before it shows up in the resource analysis calculations.