You are an implementation consultant working at a company where project schedules have been
managed primarily with Microsoft Project, on individual desktops. The “projects” theoretically have
been multiple-year projects. Your scope of work includes migrating project data from legacy
project plans and setting up project planning standards. As you look into the current Microsoft
Project plans, it becomes clear that the projects are not really multi-year projects. The plans have
been managed by creating “new” projects within the old projects by skipping a few lines in what
has become more of a program history.
What approach would you recommend to retain the legacy data (which is a mandated requirement
in the new Primavera system), while moving forward with a “one project, one plan” process?
A.
Import all MS Project plans directly into the P6 production database “as is.”
B.
Import MS Project plans but break out current in-flight work into separate projects.
C.
Create new projects only for in flight work identified in MS Project plans.
D.
Retire legacy project plans and start with new project planning standards.