Linking to summary tasks

One of our customers at work recently suggested that linking to a
summary task wasn't good practice. Does anybody agree and can suggest
why this is so?

Sometimes we have lots of lower level tasks and if a summary task
cannot be linked to then it will involve lots of seperate links.

Dale
Wed Mar 09 09:06:18 CST 2005

Andy --

Setting dependencies on summary tasks result in circular reference errors.
After you've dealt with troubleshooting your first circular reference error
in Microsoft Project, that is enough to make you NEVER want to go through
that again! Hope this helps.

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
http://www.msprojectexperts.com
"We wrote the book on Project Server"


"Andy" <wolseley6@tiscali.co.uk> wrote in message
news:bb9994df.0503090639.13289bb4@posting.google.com...
> One of our customers at work recently suggested that linking to a
> summary task wasn't good practice. Does anybody agree and can suggest
> why this is so?
>
> Sometimes we have lots of lower level tasks and if a summary task
> cannot be linked to then it will involve lots of seperate links.

davegb
Wed Mar 09 09:18:21 CST 2005

This has long been a major bone of contention in here. Some feel it is
ok. Having done schedules for over 20 years now, first by hand, later
using software, I agree with your friend. Linking summary tasks is
usually a short cut to avoid correctly identifying the true
dependencies on the project, which leads to headaches to numerous to
detail here. And it leads to circular references, as Dale said above.

John
Wed Mar 09 10:54:05 CST 2005

In article <bb9994df.0503090639.13289bb4@posting.google.com>,
wolseley6@tiscali.co.uk (Andy) wrote:

> One of our customers at work recently suggested that linking to a
> summary task wasn't good practice. Does anybody agree and can suggest
> why this is so?
>
> Sometimes we have lots of lower level tasks and if a summary task
> cannot be linked to then it will involve lots of seperate links.

Wolseley,
I might as well weigh in on the discussion. I agree wholeheartedly with
Dale, Dave and your friend. Project allows links to Summary lines and it
may seem like a good shortcut idea but usually when there is an easy
shortcut, it has consequences. It MIGHT be ok if you have a LOT of
experience with Project and are VERY careful.

The bottom line, use links on Summary lines at your own risk. How lucky
do you feel.

John
Project MVP

JackD
Wed Mar 09 11:21:41 CST 2005

I can't say I can recommend it either. If you need to do something like this
consider a start and a finish milestone as subtasks and link the subtasks to
them. It gives you the same effect as links to a summary task.

--
-Jack ... For project information and macro examples visit
http://masamiki.com/project

.
"John" <mjensen@theriver.com> wrote in message
news:mjensen-229FE2.08540509032005@msnews.microsoft.com...
> In article <bb9994df.0503090639.13289bb4@posting.google.com>,
> wolseley6@tiscali.co.uk (Andy) wrote:
>
> > One of our customers at work recently suggested that linking to a
> > summary task wasn't good practice. Does anybody agree and can suggest
> > why this is so?
> >
> > Sometimes we have lots of lower level tasks and if a summary task
> > cannot be linked to then it will involve lots of seperate links.
>
> Wolseley,
> I might as well weigh in on the discussion. I agree wholeheartedly with
> Dale, Dave and your friend. Project allows links to Summary lines and it
> may seem like a good shortcut idea but usually when there is an easy
> shortcut, it has consequences. It MIGHT be ok if you have a LOT of
> experience with Project and are VERY careful.
>
> The bottom line, use links on Summary lines at your own risk. How lucky
> do you feel.
>
> John
> Project MVP

wolseley6
Wed Mar 09 15:27:41 CST 2005

"Dale Howard [MVP]" <dale(dot)howard(at)msprojectexperts(dot)com> wrote in message news:<#MX$MmLJFHA.3404@TK2MSFTNGP10.phx.gbl>...
> Andy --
>
> Setting dependencies on summary tasks result in circular reference errors.
> After you've dealt with troubleshooting your first circular reference error
> in Microsoft Project, that is enough to make you NEVER want to go through
> that again! Hope this helps.
>
> --
> Dale A. Howard [MVP]
> Enterprise Project Trainer/Consultant
> http://www.msprojectexperts.com
> "We wrote the book on Project Server"
>
>
> "Andy" <wolseley6@tiscali.co.uk> wrote in message
> news:bb9994df.0503090639.13289bb4@posting.google.com...
> > One of our customers at work recently suggested that linking to a
> > summary task wasn't good practice. Does anybody agree and can suggest
> > why this is so?
> >
> > Sometimes we have lots of lower level tasks and if a summary task
> > cannot be linked to then it will involve lots of seperate links.


Thanks for the reply Dale.

Yes I have had to deal with circular relationships before now;
however, not anything to do with linking to Summary tasks.

I notice you are Enteprise Project Trainer/Consultant. I am working on
a very large/complex programme at the moment with a very poor use of
scheduling across the Enteprise. I suppose you would recommend Project
server for us but what if current mindset/culture are against this? I
have tried to get people interested but with no success.

Thanks again,

Andy

Dale
Wed Mar 09 16:45:06 CST 2005

Andy --

If the current mindset and culture are against implementing an enterprise
project management tool such as Project Server, then it would probably be a
huge waste of time and money. There needs to be organization commitment,
among other things, before the implementation has a chance of success.
Thanks for trying, however. :)

--
Dale A. Howard [MVP]
Enterprise Project Trainer/Consultant
http://www.msprojectexperts.com
"We wrote the book on Project Server"


"Andy" <wolseley6@tiscali.co.uk> wrote in message
news:bb9994df.0503091327.448a7034@posting.google.com...
> "Dale Howard [MVP]" <dale(dot)howard(at)msprojectexperts(dot)com> wrote in
> message news:<#MX$MmLJFHA.3404@TK2MSFTNGP10.phx.gbl>...
>> Andy --
>>
>> Setting dependencies on summary tasks result in circular reference
>> errors.
>> After you've dealt with troubleshooting your first circular reference
>> error
>> in Microsoft Project, that is enough to make you NEVER want to go through
>> that again! Hope this helps.
>>
>> --
>> Dale A. Howard [MVP]
>> Enterprise Project Trainer/Consultant
>> http://www.msprojectexperts.com
>> "We wrote the book on Project Server"
>>
>>
>> "Andy" <wolseley6@tiscali.co.uk> wrote in message
>> news:bb9994df.0503090639.13289bb4@posting.google.com...
>> > One of our customers at work recently suggested that linking to a
>> > summary task wasn't good practice. Does anybody agree and can suggest
>> > why this is so?
>> >
>> > Sometimes we have lots of lower level tasks and if a summary task
>> > cannot be linked to then it will involve lots of seperate links.
>
>
> Thanks for the reply Dale.
>
> Yes I have had to deal with circular relationships before now;
> however, not anything to do with linking to Summary tasks.
>
> I notice you are Enteprise Project Trainer/Consultant. I am working on
> a very large/complex programme at the moment with a very poor use of
> scheduling across the Enteprise. I suppose you would recommend Project
> server for us but what if current mindset/culture are against this? I
> have tried to get people interested but with no success.
>
> Thanks again,
>
> Andy

DavidC
Thu Mar 10 17:19:02 CST 2005

I have recently had to create a summary of various non-consecutive tasks and
to refelect the summary tasks, in order for the client to give the contractor
an overview of start and finish dates. I created linked tasks using the
start date for the first task in a summary task and the finish date of the
task which creates the end date for the summary task. That way the link is
connected to the base data and not a microsoft calculated data. Seems to
work as lomg as the calendar set for the task is the same as the one for the
set of tasks. Found one glitch though where the first task in the summary
used a night shift calendar but the remaining tasks used an ordinary shift
calendar. The dates and times were correct but the linked task would not
follow correctly as it used whatever calender it was assigned to 'reset' the
start and finish dates.

"JackD" wrote:

> I can't say I can recommend it either. If you need to do something like this
> consider a start and a finish milestone as subtasks and link the subtasks to
> them. It gives you the same effect as links to a summary task.
>
> --
> -Jack ... For project information and macro examples visit
> http://masamiki.com/project
>
> ..
> "John" <mjensen@theriver.com> wrote in message
> news:mjensen-229FE2.08540509032005@msnews.microsoft.com...
> > In article <bb9994df.0503090639.13289bb4@posting.google.com>,
> > wolseley6@tiscali.co.uk (Andy) wrote:
> >
> > > One of our customers at work recently suggested that linking to a
> > > summary task wasn't good practice. Does anybody agree and can suggest
> > > why this is so?
> > >
> > > Sometimes we have lots of lower level tasks and if a summary task
> > > cannot be linked to then it will involve lots of seperate links.
> >
> > Wolseley,
> > I might as well weigh in on the discussion. I agree wholeheartedly with
> > Dale, Dave and your friend. Project allows links to Summary lines and it
> > may seem like a good shortcut idea but usually when there is an easy
> > shortcut, it has consequences. It MIGHT be ok if you have a LOT of
> > experience with Project and are VERY careful.
> >
> > The bottom line, use links on Summary lines at your own risk. How lucky
> > do you feel.
> >
> > John
> > Project MVP
>
>
>