Best Approach for "Sub Projects"

D

dee

I am using Project Pro 2003 and Project Server 2003 and need some advice.

Most of our projects will be the same thing - the manufacturing of products.
So, I want to put together a template that the PMs can use each time there
is a new product development project.

Each project contains phases that a particular department is responsible
for. So, we need to "hand off" at the completion of one phase to the person
responsible for the next phase.

My questions are:

1.
Do I create a template with RBS coding with general tasks, then use the
resource replacement wizard to add the actual resources. The tasks will also
be modified to reflect the actual product concerned.

This is the approach that makes sense to me - are there any pitfalls I
should avoid?

2.
In this structure, do I simply have one project (without subprojects) that
is divided into phases and assign a team lead to each phase?

I imagine the project itself will have a PM, then a team lead from each
department who is responsible for their phase, with the team members of that
phase/department reporting to their team lead.

Does this sound correct? Any advice would be greatly appreciated.
 

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.

Ask a Question

Top