Timephased Resource Information
While effort and base capacity is timephased, the associated resource information such as Team Name, Resource Department, RBS, and Timesheet Manager are not. This means that as staff move about the organization, our reports will only ever show their effort as associated with their current state of employment. This gap causes concern and inaccurate historical reports.
Question from Leadership: "How many QA hours did that last ERP Program (of multiple projects) need?" or "How has the balance of operational effort, support effort, and project effort changed over the last three years?"
Answer today: We're not sure. Two of them are now [new dev language here] developers and one's an application administrator, so my report shows you that 1500 hours of [new dev language here] developer effort were expended during that time... I know... we didn't even employ a [new dev language here] developer during that time, but that person who was on QA took on that new role starting on YYYYMMDD, so if you make this manual adjustment to this portion of the report when you want this type of answer, and move that over to there, then everything looks good. No, I know... You can totally trust the reports once they're massaged.... well, mostly.
....this ruins the credibility of the data, and once that happens, one of the major arguments for encouraging time tracking starts to erode.
I'd see this as being implemented exactly how you can adjust the max units of a resource: "just" enlarge that window and add in key pieces of resource information. I'd default it with at least Team, but make it admin-selectable in PWA settings, and allow the organization to zero to many of their own custom resource fields as well. For example, we have one called "staff type" which would be very handy in the same types of reports.
Ian Bruckner commented
Here's someone looking for something similar for another custom resource field called internal labor rate:
Ian Bruckner commented
Came across another suggestion that made me consider that another field would be helpful for each row: a comment field to help you or others recall why units changed for a given date range if no other attributes make the explanation clear. For an example, see https://microsoftproject.uservoice.com/forums/218133-microsoft-project/suggestions/13475979-manage-negative-capacities#comments