do task constraints constrain subtasks?

[Chaps]

Will a task constraint automatically constrain all of their subtasks?

 

[Rod Gill]

Maybe for raw beginners, but linking to summary tasks is perfectly OK. for
example if none of the tasks in one group of tasks can start until all the
tasks in another group have finished, the simple solution is to link the
summary tasks of the two groups. One simple link. Without that option you
need to have every task in the first group linked to every task in the
second group directly or indirectly which is a real mess and doe not
communicate what is happening.

I regularly use and teach this and it causes no problems and displays a more
realistic picture of what is meant to happen.

 

[John]

Maybe for raw beginners, but linking to summary tasks is perfectly OK. for
example if none of the tasks in one group of tasks can start until all the
tasks in another group have finished, the simple solution is to link the
summary tasks of the two groups. One simple link. Without that option you
need to have every task in the first group linked to every task in the
second group directly or indirectly which is a real mess and doe not
communicate what is happening.

I regularly use and teach this and it causes no problems and displays a more
realistic picture of what is meant to happen.
--

Rod Gill
Project MVP
Visit www.msproject-systems.com for Project Companion Tools and more

Rod,
I guess I take exception to the statement that, "...linking to summary
lines is perfectly OK". Unfortunately very few users are willing to put
themselves into the category of "raw beginner", because even "seasoned"
users can very easily run afoul with summary line links. Sure a user can
"get away" with linking summary lines just like it is fine to use paste
links - as long as the user has exceptional discipline - not a
"built-in" human trait. I think our best consul is to refer users to our
FAQ 48 on summary line links (http://www.mvps.org/project/faqs.htm)
where the pitfalls are highlighted but the rare exception is noted.

John
Project MVP

 

[davegb]

Maybe for raw beginners, but linking to summary tasks is perfectly OK.

I have to disagree with Rod on this. You might get away with it for a
while, but linking Summary lines will often create serious problems in
your schedule. Summary links are the most common cause of circular
links. They also create problems in resource leveling, since there are
rarely resources assigned to Summary lines, and leveling can get rather
convoluted. It also causes problems with even having a MEANINGFUL
critical path. One of the major uses of the Critical Path is to help
the PM prioritize between tasks. The Critical Path tasks have first
priority (other things also need to be taken into account in this
decision). If your Critical Path goes through a Summary line, which
tasks in that part of the project are Critical? You don't know.


for

example if none of the tasks in one group of tasks can start until all the
tasks in another group have finished, the simple solution is to link the
summary tasks of the two groups. One simple link. Without that option you
need to have every task in the first group linked to every task in the
second group directly or indirectly which is a real mess and doe not
communicate what is happening.

The problem of one group of sub-tasks having to follow another group of
sub-tasks is easily solved by putting a milestone as a successor to any
task in the sub-group that could finish last, then linking that
milestone to a milestone that is a predecessor to the sub-tasks that
need to follow. Easy, and won't get you into any trouble.

I agree with the previous poster who advised NEVER to link or constrain
summary lines.