phases/master project and Project 2007

[Ryan Rupert]

KEYWORDS
*Master project
*Portfolio
*Programs
*Linked Projects
*Inserted Project
*Consolidated Project

EXPLANATION
-I am just now broaching this subject for our solution,
for every project we perform phases (Discovery, Analysis,
Design, Implementation)
-in effect these are 4 seperate projects that may or may
not make it to the last phase Implementation, we could
have a client approve the Discovery phase but then not
approve Analysis so we would stop there
-we will go from a Proposal process (using Project 2007
on MOSS 2007), to the first phase Discovery which will be
in effect the "master project", budgeting, resources, reports,
documents will all be independant of any subsequent phase
but of course would be "logically" associated if another
project phase were to be approved by a client
-I like the idea of creating a project template that will include
all of these phases, but I would only create a Project Workspace
for a given phase if that phase is approved by my client, so a
Master Project plan could have generic tasks for future phases
but would just not have any resources or time allocated until
inception
-so, I am envisioning a Project Workspace and Project "master"
that starts with my phase "Discovery" and in the end, potentially
has sub-workspaces/sub-projects for each of the subsequent
phases
-now, each subseqent phase would have activity that is
interrelated and in most cases dependant (predecessors, etc)
with the previous phase so I want them to remain logically
associated, I am thinking Master Project and sub-projects is
the way to do this

QUESTION
-is my explanation above enough info to point me in the right direction

 

[Scott m Wagner - EPM Consulting Services]

Ryan,

Ryan,

As I see it this approach is certainly "one" possible approach. It would not
however be mine. There have always been and will always be issues and
potential issues and risk when working with "Master" projects.

There are some rare cases that I do find Master projects to be “just what
the doctor ordered" but I do not believe, from what you stated, that is the
case here.

I see no reason why you do not just crate a normal project plan template
with various phases, use generic resources until the work is approved and
then populate the resources once work is approved. This will help separate
actual from planned. There are many other things you can do as well. I
seriously recommend you speak with a Microsoft Project Partner for best
practices and to help you with a go forward strategy.

As for SharePoint, I would recommend a new “Site Template†be used that
contains specific information so you could separate the information
(Documents, risks, issues and other information) by stage but also be able to
provide a holistic kind of Project view. Again, a good partner is recommended.

Hope the information here helps lead you in the right direction.

 

[Ryan Rupert]

-I know I have many options, thanks for the info