At this point, just getting those who are suppose to manage to
republish is tough enough, but somebody high-up looked at this and
raises concerns.
Project Managers can have different employment relationships. One
might be a corporate hand, several others might be consultants.
Perhaps the consultants are also resources on a key project managed by
a corporate manager. Their ability to republish and take management of
a task to which they are assigned will allow them to accept time that
may later be the basis for payments, and it looks like the corporate
manager could be taken out of an approval loop without any
notification.
Add to this the fact that the out-of-the-box solution doesn't make it
real clear who is managing what task....
Anything different about this in the next version?
I'm also seeing that many of the corporate project managers are mostly
interested in time approvals. They are content to delegate the
staffing of projects and task scheduling. The ability for a
subordinate to "push" the management of a task or resource back to a
manager while making changes and publishing them would be very useful.
The manager could receive notification of the push along with a
description of the updates such as what goes to resources upon
republishing, now.
No doubt there are some scripting solutions or database queries that I
can create that might generate alerts and ownership reports. I get a
bit seasick thinking about it though.
J
