While working on a large project with 25+ individual project schedules, I discovered some nuances within cross-project linking. This may be common knowledge for some of you experienced project managers, but if I can save anyone the frustration that I incurred, then the following information is worth sharing.
First and most importantly, have one dedicated resource in charge of all cross-project tasks linking. The old saying, “Too many hands in the pie…” was created for a very good reason. If you do not incorporate the aforementioned standard, be prepared to deal with the following:
- Cross-project tasks linked to files that have been archived, backed-up or copied. One task may be linked multiple times to the same task. As the file ebbs and flows with changes in MS Project, the task name will remain the same, but the task ID number may change.
- Cross project tasks linked to unknown file path names. This can occur from a project manager conducting the following tasks:
- Downloading their file to a thumb-drive and;
- Diligently taking their file home to “work from home” on a non-standardized application and;
- Uploading their file to a home computer and then making changes and links within their project and;
- The major fatal error…is re-uploading their file to the shared drive server at the workplace.
- As stated above and worth re-stating, have one person responsible for all cross-project tasks linking.
- When linking tasks from two separate files, practice the following steps:
1. Make sure the two separate files are in a consolidated project plan or master project plan.
2. Once the files have been placed into a consolidated project or master project, click on the task that will be an external predecessor. Next, hold down the control button and click on the task that will be in the external successor.
3. Click the link button on your standard tool bar. The two tasks are now linked.
4. “Task relationships between project plans look similar to links between tasks within a project plan, except that external predecessor and successor tasks have gray task names and Gantt bars. Such tasks are sometimes referred to as ghost tasks because they are not linked to tasks within the project plan, only to tasks in other project plans” (C. Chatfield and T. Johnson, 2007).
Now that you have been given a quick snippet of cross project linking, link away! But remember to follow Cross Project Linking Protocol!
Chatfield, Carl and Johnson, Timothy (2007). Microsoft Office Project 207 Step by Step. Microsoft Press, Redmond, Washington.