Some thoughts regarding scheduling, end-user autonomy
I think the PM/system can suggest/propose optimal periods for specific tasks done (by group/individiual), but that the final schedule should be made/confirmed individually by each participant (and changeable by them or their "supervisor").
This is important for projects that have external resource components (participating clients, subcontractors, temporary/part-time employees etc.) --and might be overlooked by organizations that tend to operate top-down authoritarian style projects. [I must do "this" because the computer says so.]
It's been mentioned before, but it's important to re-iterate:
In order to get everyone to participate fully in using the system, the system needs to cater to the end-users using it over any conveniences extended to the PM(s) (ie. respect the user--allow them the same degree of freedom as is available outside the system). This means that the system should offer users over-riding automony, even if it is at their own expense (and to the detriment of the project). The PM could be notified of such changes (or interest in changes), and address them accordingly.
