Hi all.
On our project schedules our PMs usually put a 'bucket' task for charging project management time (meetings, status reporting, admin activities, etc).
The working process today is to run these tasks the duration of the project, set the load pattern to uniform to spread the hours (a couple per week, whatever they need), then set it back to a fixed loading pattern in order to have any unused hours 'burn off'.
This works OK. We key these tasks with an ID starting with 'paa_' (project admin activity) to be able to exclude these from any portlets and reports that we build, but these tasks muddy the waters for out of the box functionality such as critical path, EVM, etc.
Has anyone else wrestled with this already and has a better approach to share?
Thanks!