One Project, Multiple Managers = Dynamic change management

One of our customers has development centers in San Diego and India. They have a project where the top-level manager is located in San Diego, while sub-projects are delegated to teams both in San Diego and in India.

When they first started using LiveProject, the top-level manager uploaded one project file, and participants through the organization started filing changes. As a consequence, this manager had to approve (or reject) all of these, even changes he did not know anything about. The situation became worse as he had to follow-up with sub-managers to check that changes were correct.

After a bit of consulting, we were able to advise him of a better solution. He split his Project file into a main project, and added 4 sub-project files to that. He then uploaded all these 5 project files himself (thus effectively becoming the manager of them all). Subsequently he manually assigned each of the sub-projects to each of his 4 sub-managers.

Participants would still 'monitor' the main file (which contains the entire project), but changes that happened within a subproject are now routed to the correct sub-manager. LiveProject does this routing by default, so the resolution was quite simple.