Overview | Example | Step 1 | Step 2 | Step 3 | Step 4 | Step 5 |
| Step 6 |
| Step 7 |
| Step 8 |
Master Project - Program Management -> Example
MS Project Server 2007 supports master projects and allows us to save and publish to the server. Letís say, if you know there will be the new effort getting started in your organization and there will be number of projects will be associated with that new effort. In this scenario, it is always best practice to have master project by inserting those individual projects within master. This will give opportunity to give complete visibility of program status by viewing the consolidate schedule view on master project. This feature is very helpful to Program Managers and Project Management Office.
Please remember Master Project also called as Program Plan in MS Project Server 2007.
The ideal method of managing programs in MS Project Server 2007 is, first you should have program plan (Master Project) before save the sub projects into server.
You can create the consolidated project at any time. (You can still use published projects as sub projects for master project).
If you want to have structured workspaces for your program, please don't create the workspaces for individual sub projects till you do not have master project workspace.
By creating the sub project workspaces within program workspace, you will get the ability to create the program dashboard (using reporting tool like SQL Reporting Services) by consolidating issues, risks and deliverables etc.
Suppose your organization announces new program to manage the various system upgrades in IT organization. They named program as IT System Upgrade Program. The following various systems upgrades are identified as a part of the program.
The following sequence of steps will illustrate the structured approach and demonstrate the best practice on managing the program by having program plan (Master Project) in MS Project Server 2007.
- Invoice system upgrade
- Product warranty upgrade
- OP systems upgrade
Step 7: Publish sub projects as sub-workspaces within program
Step 8: Program Tracking