One way would be to create a Master Project containing links to all of
the projects within the Programme.
This would allow you to look at resource commitments across the entire
Programme as well as create dependencies across different projects
within the Programme.
What do you hope to achieve from the consolidation?
we would use it mainly for standardisation of approach, easiness of
printing, resources committment. also i need to find a way to pictorially
represent project interdependencies at programme level. something like a
gantt chart that shows me the interdependencies at project level within our
programme. please can you advise further on this last point, how to achieve
it. Many thanks
Well if you insert links to the plans in the master and create links
between the tasks in the various plans to create the Programme Network
Diagram then you have done that.
I guess the point is that you don't want to have to print out all the
tasks to show the dependencies. You could filter out the tasks you
don't want to display so that you are left only with those for which
there are cross-project dependencies.
An alternative approach might be to create a milestone section at the
top of the project linked to each of the projects showing key events.
You could also group the milestones under summary tasks which would then
largely represent the project-level summaries from each of the
individual projects.
For those milestones representing dependencies you could then suitable
descriptions such as "Starts when Task A from Project X completes".
The network diagram is one of the views on the View menu. It will be
pretty unwieldy for a substantial programme though. I really meant that
the links can be used to show inter-project task dependencies as will as
those within any one project.
Ask a Question
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.