Duration in Summary Task

[Shahriar N k]

Is there any way to not include lag time in the duration value for summary
tasks?

Here is some more detail:
My projects are IT projects.

A QA(quality assurance) person can test a task after a D(developer)
completes his task. But QA testing occours the day after D finishes work. So,
if D finishes
today QA will test tomorrow.

To schedule such a situation, i have made D(task) predecessor of QA (task)
with one day lag time.

But this lag time shows in the total time(duration) of the summary task. in
other
words the summary task duration also has this lag time - which i dont want.

so, is there any way to make the summary task ignore the lag(/lead) time in
its subtasks?
Eagerly waiting for your reply.
thank you.

 

[ProjmanZA]

Is there any way to not include lag time in the duration value for summary
tasks?

Here is some more detail:
My projects are IT projects.

A QA(quality assurance) person can test a task after a D(developer)
completes his task. But QA testing occours the day after D finishes work.So,
if D finishes
today QA will test tomorrow.

To schedule such a situation, i have made D(task) predecessor of QA (task)
with one day lag time.

But this lag time shows in the total time(duration) of the summary task. in
other
words the summary task duration also has this lag time - which i dont want.

so, is there any way to make the summary task ignore the lag(/lead) time in
its subtasks?
Eagerly waiting for your reply.
thank you.

Shahriar

As far as i am aware what you need aint going to happen, as the
Project Summery task depicts the TOTAL duration of the project, Which
is truely what one
needs. Have you mayby tried using constrains ? Not the wizest thing to
do but it could possibly assist you, but it will ALSO impact the total
project duration.

Another thing you could perhaps do is to insert another task into the
schedule but this will ALSO impact the Duration.

So unless i do not know of that functionality you are going to have to
manage it some other way.

Regards
Andre

 

[Jim Aksel]

This may look a little ugly but it should work. First, adding a day lag may
be causing you some problems. If Developer finishes his task at 1PM, the QA
test (with 1 day lag) starts tomorrow --- at 1PM. Also, if Developer finishes
at 5PM on Monday, adding 1 day lag will start test on Wednesday.

If testing must always start "tomorrow" at 8AM try this:

Create a new calendar with exactly one minute of work each normal work day
at 5:01PM (notice this is later than the 5PM quit for the regular work
calendar. Now add a new task between Develop and Test, let's call it "Ready
For Test" ... make it a milestone. Assign the new calander to the the "Ready
for Test" task.... it will happen at 5:01PM. Now link the three tasks Dev,
"Ready for Test" and QA Test all as FS.

You could also do the same thing with 7:59AM if that works better for you.
There has been some discussion in this newsgroup about this topic. If you
run into problems, try making the "Ready for Test" task a regular task of 1
minute duration without resource assignments.
--
If this post was helpful, please consider rating it.

Jim Aksel, MVP

Check out my blog for more information:
http://www.msprojectblog.com