...
Headcount is metric that looks useful and a lot of people gravitate towards it. However, it is a field we often steer people away from in favor of FTEs or and REs. As with FTEs and REs, the The reporting time interval affects how we do headcount . But for headcount, that methodology and the methodology we use ends up not being very useful. For example, say your report is looking at headcount by the month. Projector returns a whole value (1) for each resource that is in that month. Imagine Jim works 1 hour in June and Sally works 100 hours in June. Each give you a headcount of 1, for a total of two. FTEs and REs are much more useful as they give you weighted values relative to the time period.In addition, because of the way pivot tables aggregate data, if you are breaking the data up by row fields, and the resource switches in the middle of a time bucket, they will get double counted. For example, you are looking at headcount by Title
| Warning | ||
|---|---|---|
| ||
Pivot tables aggregate data by looking at each unique row in the pivot cache and summing them. If you are drilling into headcount through multiple row fields, this can cause your headcount to be too high. For example, your report shows headcount, by title, by month. Sarah's title changes from Manager to Sr. Manager |
...
in the middle of the month. This |
...
generates two rows |
...
in the pivot cache. One for each title. Her headcount will be 2 for that month and likely not what you want. |