Master Project Question

[Sinister]

I've read in a couple of books that you shouldn't change subproject data in a
master project because it could produce undesirable results. Is this true?
And what are these undesirable results?

 

[Dale Howard [MVP]]

Sinister --

Out of curiosity, what books made that statement? How can you manage a
project if you are not free to make changes to it? Perhaps what the authors
were thinking of was subprojects that have cross-project dependencies, where
a task in one project is dependent on a task in another project. If you
make a change in one of the subprojects, that could change the schedule in
the other project. But that's not a bad thing, quite frankly. Hope this
helps.

 

[Jim Aksel]

To confirm Dale's point.... we do it here all the time, no problem. It is
our preferred method.
--
If this post was helpful, please consider rating it.

Jim
It''s software; it''s not allowed to win.

Visit http://project.mvps.org/ for FAQs and more information
about Microsoft Project

 

[Martin Wilkinson]

I've used Project on and off on several projects for around 10 years, and
don't claim to be an expert, but for what it's worth, I would do almost
anything to avoid using subprojects, unless a single project got ridiculously
large. (Using MSP 2000, don't know if subproject management improved in later
versions). It's a shame because using Subprojects is often an ideal way to
break a project down and allow individual Work Package owners to modify their
schedules independently.

The problems usually culminate in seriously corrupted MSP files (in my
experience).

However, if other people use them successfully, I'm pleased for them!