Totally feel you on the mapping hours. We thought we had a clean list, then spent weeks discovering "tribal knowledge" accounts nobody had documented. It blew the phase one timeline.
I'd also love to hear how teams track the hours cross-department. In my old role we used a shared spreadsheet, but it was a mess for blocking tickets from other teams. How do you attribute that time? Is it just logged as project overhead?
Great question. We didn't track it to that level of detail for our BeyondTrust rollout, and now I wish we had. The licensing cost was easy, but the time lost to cross-team meetings and security reviews was invisible on the budget sheet.
How do you even capture that? Is it just logged as project overhead in your timesheets? I saw someone earlier mention using a Grafana dashboard for tracking project hours, which is clever. Might steal that idea if I ever have to do this again.