project 98 work:duration bug?

[jonnysaf]

I have a fixed amount of work to do, so I enter it in the 'work' field. I
also make sure that my task type is 'fixed work'. I then allocate 2 resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently random
way? Also the 'duration' then adopts one if these random splits, which have
no bearing on how long it will take to do the task with two resources applied
at 100% (ie, one would hope, half of the work time!)

 

[John]

I have a fixed amount of work to do, so I enter it in the 'work' field. I
also make sure that my task type is 'fixed work'. I then allocate 2 resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently random
way? Also the 'duration' then adopts one if these random splits, which have
no bearing on how long it will take to do the task with two resources applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[jonnysaf]

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm still a
little confused by the way you enter the task; maybe my assumption of what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for all
tasks as well as the 'work'. I want to create a program that is work/resource
driven, rather than time driven; ie I want to enter a fixed amount of work,
apply a resource, and then have MSP tell me the resulting duration. If the
duration is too long, then I will need to add another resource and so on.

What am I doing wrong?

js

I have a fixed amount of work to do, so I enter it in the 'work' field. I
also make sure that my task type is 'fixed work'. I then allocate 2 resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently random
way? Also the 'duration' then adopts one if these random splits, which have
no bearing on how long it will take to do the task with two resources applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[Jan De Messemaeker]

Hi,

Then leave the duration at the standard 1d? , enter the resource, then
change work; duration is recalculated.
HTH

--
Jan De Messemaeker, Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
For FAQs: http://www.mvps.org/project/faqs.htm

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm still a
little confused by the way you enter the task; maybe my assumption of what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for all
tasks as well as the 'work'. I want to create a program that is work/resource
driven, rather than time driven; ie I want to enter a fixed amount of work,
apply a resource, and then have MSP tell me the resulting duration. If the
duration is too long, then I will need to add another resource and so on.

What am I doing wrong?

js

I have a fixed amount of work to do, so I enter it in the 'work' field. I
also make sure that my task type is 'fixed work'. I then allocate 2 resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently random
way? Also the 'duration' then adopts one if these random splits, which have
no bearing on how long it will take to do the task with two resources applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[John]

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm still a
little confused by the way you enter the task; maybe my assumption of what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for all
tasks as well as the 'work'. I want to create a program that is work/resource
driven, rather than time driven; ie I want to enter a fixed amount of work,
apply a resource, and then have MSP tell me the resulting duration. If the
duration is too long, then I will need to add another resource and so on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John

I have a fixed amount of work to do, so I enter it in the 'work' field. I
also make sure that my task type is 'fixed work'. I then allocate 2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently
random
way? Also the 'duration' then adopts one if these random splits, which
have
no bearing on how long it will take to do the task with two resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[jonnysaf]

John, It's all good help!

I have another question: Can I enter a task to start when another task is
75% complete (and always have it at 75%, rather than by date, even when the
basetask changes its own start or finish due to other constraints)? Please
dont tell me I need to split the basetask in two...

js

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm still a
little confused by the way you enter the task; maybe my assumption of what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for all
tasks as well as the 'work'. I want to create a program that is work/resource
driven, rather than time driven; ie I want to enter a fixed amount of work,
apply a resource, and then have MSP tell me the resulting duration. If the
duration is too long, then I will need to add another resource and so on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John

I have a fixed amount of work to do, so I enter it in the 'work' field. I
also make sure that my task type is 'fixed work'. I then allocate 2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently
random
way? Also the 'duration' then adopts one if these random splits, which
have
no bearing on how long it will take to do the task with two resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[Jack Dahlgren]

Yes, you can to a certain extent. Do this. Create a standard Finish to Start
dependency. Double click on the dependency line and set the lag to be "-25%"

I'm not 100% certain how it calculates the 75% so there might be some times
when it is not what you expect (split tasks etc.) but give it a try.

-Jack Dahlgren
http://zo-d.com/blog

John, It's all good help!

I have another question: Can I enter a task to start when another task is
75% complete (and always have it at 75%, rather than by date, even when the
basetask changes its own start or finish due to other constraints)? Please
dont tell me I need to split the basetask in two...

js

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm still a
little confused by the way you enter the task; maybe my assumption of what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for all
tasks as well as the 'work'. I want to create a program that is work/resource
driven, rather than time driven; ie I want to enter a fixed amount of work,
apply a resource, and then have MSP tell me the resulting duration. If the
duration is too long, then I will need to add another resource and so on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John

:

I have a fixed amount of work to do, so I enter it in the 'work' field. I
also make sure that my task type is 'fixed work'. I then allocate 2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently
random
way? Also the 'duration' then adopts one if these random splits, which
have
no bearing on how long it will take to do the task with two resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[John]

John, It's all good help!

I have another question: Can I enter a task to start when another task is
75% complete (and always have it at 75%, rather than by date, even when the
basetask changes its own start or finish due to other constraints)? Please
dont tell me I need to split the basetask in two...

jonnysaf,
It looks like Jack took this one but let me offer an alternate. I don't
like the concept of task lead since in my mind it borders on prediction
of the future. Yeah I know, just creating a plan requires a certain
amount of prediction but I still don't like the concept of "lead" in a
link.

The following will also work:
[predecessor task]SS + 75%

Hope this helps.
John

js

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm still a
little confused by the way you enter the task; maybe my assumption of
what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for all
tasks as well as the 'work'. I want to create a program that is
work/resource
driven, rather than time driven; ie I want to enter a fixed amount of
work,
apply a resource, and then have MSP tell me the resulting duration. If
the
duration is too long, then I will need to add another resource and so on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John

:

I have a fixed amount of work to do, so I enter it in the 'work'
field. I
also make sure that my task type is 'fixed work'. I then allocate 2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently
random
way? Also the 'duration' then adopts one if these random splits,
which
have
no bearing on how long it will take to do the task with two resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear
that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a
fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer
holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[jonnysaf]

Thanks guys, this is great help!

One more question:

I have to create an event at points 50% and 75% complete. During this
process all work will stop on the main project as all resources will be
directed at the event (a draft document issue).

1. Is it possible to create a 'pause' within all tasks within which this
event can happen?

2. Can I create an event which shows graphically as a vertical task / line?

js

John, It's all good help!

I have another question: Can I enter a task to start when another task is
75% complete (and always have it at 75%, rather than by date, even when the
basetask changes its own start or finish due to other constraints)? Please
dont tell me I need to split the basetask in two...

jonnysaf,
It looks like Jack took this one but let me offer an alternate. I don't
like the concept of task lead since in my mind it borders on prediction
of the future. Yeah I know, just creating a plan requires a certain
amount of prediction but I still don't like the concept of "lead" in a
link.

The following will also work:
[predecessor task]SS + 75%

Hope this helps.
John

js

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm still a
little confused by the way you enter the task; maybe my assumption of
what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for all
tasks as well as the 'work'. I want to create a program that is
work/resource
driven, rather than time driven; ie I want to enter a fixed amount of
work,
apply a resource, and then have MSP tell me the resulting duration. If
the
duration is too long, then I will need to add another resource and so on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John


:

I have a fixed amount of work to do, so I enter it in the 'work'
field. I
also make sure that my task type is 'fixed work'. I then allocate 2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and apparently
random
way? Also the 'duration' then adopts one if these random splits,
which
have
no bearing on how long it will take to do the task with two resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a work
calendar that is different from the task calendar. Project will then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear
that
way. It is only software and it responds to a very defined set of rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10 day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a
fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a second
resource. Now Project modifies it algorithm slightly. It no longer
holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on this
task) for a total of 12 hours/day for both resources. Then for the 40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33 days.
If you want the first assignment to change the duration by keeping work
and unit assignment level fixed, then you will need to re-assign the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the duration
will drop to 5 days for 40 hours of work. If you then assign a second
resource to that task at 100%, Project will further drop the duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work and
units then developing and maintaining a plan is a little easier - at
least in theory

Hope this helps.
John
Project MVP

 

[John]

Thanks guys, this is great help!

One more question:

I have to create an event at points 50% and 75% complete. During this
process all work will stop on the main project as all resources will be
directed at the event (a draft document issue).

1. Is it possible to create a 'pause' within all tasks within which this
event can happen?

2. Can I create an event which shows graphically as a vertical task / line?

js

jonnysaf,
It seems like a pretty small focused project if everybody stops what
they are doing to attend/work on the "events". Nonetheless, doing what
you want should be possible. I haven't actually tried this so I'll make
a disclaimer first but take a look at the Stop and Resume fields. It
sounds like you should be able to enter a mass stop date for all tasks
at the first event (enter the date and do a fill-down). When it's over,
do a mass resume date for all tasks. Repeat at the second event.

As far as setting up the two events, I would use the method I described
(or Jack's method if you prefer) for an event milestone at each point.
You can show a vertical line at each event but you will have to draw it
in using the drawing feature of Project, unless you can declare the
Status Date as the event date. In the latter case, go to
Format/Gridlines.

Hope this helps.
John
Project MVP

John, It's all good help!

I have another question: Can I enter a task to start when another task is
75% complete (and always have it at 75%, rather than by date, even when
the
basetask changes its own start or finish due to other constraints)?
Please
dont tell me I need to split the basetask in two...

jonnysaf,
It looks like Jack took this one but let me offer an alternate. I don't
like the concept of task lead since in my mind it borders on prediction
of the future. Yeah I know, just creating a plan requires a certain
amount of prediction but I still don't like the concept of "lead" in a
link.

The following will also work:
[predecessor task]SS + 75%

Hope this helps.
John

js

:

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm
still a
little confused by the way you enter the task; maybe my assumption
of
what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for
all
tasks as well as the 'work'. I want to create a program that is
work/resource
driven, rather than time driven; ie I want to enter a fixed amount
of
work,
apply a resource, and then have MSP tell me the resulting duration.
If
the
duration is too long, then I will need to add another resource and so
on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John


:

I have a fixed amount of work to do, so I enter it in the 'work'
field. I
also make sure that my task type is 'fixed work'. I then allocate
2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and
apparently
random
way? Also the 'duration' then adopts one if these random splits,
which
have
no bearing on how long it will take to do the task with two
resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a
work
calendar that is different from the task calendar. Project will
then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear
that
way. It is only software and it responds to a very defined set of
rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10
day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a
fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a
second
resource. Now Project modifies it algorithm slightly. It no longer
holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on
this
task) for a total of 12 hours/day for both resources. Then for the
40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33
days.
If you want the first assignment to change the duration by keeping
work
and unit assignment level fixed, then you will need to re-assign
the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the
duration
will drop to 5 days for 40 hours of work. If you then assign a
second
resource to that task at 100%, Project will further drop the
duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work
and
units then developing and maintaining a plan is a little easier -
at
least in theory

Hope this helps.
John
Project MVP

 

[jonnysaf]

Excellent. Thanks for all the advice!

Thanks guys, this is great help!

One more question:

I have to create an event at points 50% and 75% complete. During this
process all work will stop on the main project as all resources will be
directed at the event (a draft document issue).

1. Is it possible to create a 'pause' within all tasks within which this
event can happen?

2. Can I create an event which shows graphically as a vertical task / line?

js

jonnysaf,
It seems like a pretty small focused project if everybody stops what
they are doing to attend/work on the "events". Nonetheless, doing what
you want should be possible. I haven't actually tried this so I'll make
a disclaimer first but take a look at the Stop and Resume fields. It
sounds like you should be able to enter a mass stop date for all tasks
at the first event (enter the date and do a fill-down). When it's over,
do a mass resume date for all tasks. Repeat at the second event.

As far as setting up the two events, I would use the method I described
(or Jack's method if you prefer) for an event milestone at each point.
You can show a vertical line at each event but you will have to draw it
in using the drawing feature of Project, unless you can declare the
Status Date as the event date. In the latter case, go to
Format/Gridlines.

Hope this helps.
John
Project MVP

John, It's all good help!

I have another question: Can I enter a task to start when another task is
75% complete (and always have it at 75%, rather than by date, even when
the
basetask changes its own start or finish due to other constraints)?
Please
dont tell me I need to split the basetask in two...

jonnysaf,
It looks like Jack took this one but let me offer an alternate. I don't
like the concept of task lead since in my mind it borders on prediction
of the future. Yeah I know, just creating a plan requires a certain
amount of prediction but I still don't like the concept of "lead" in a
link.

The following will also work:
[predecessor task]SS + 75%

Hope this helps.
John

js

:

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm
still a
little confused by the way you enter the task; maybe my assumption
of
what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for
all
tasks as well as the 'work'. I want to create a program that is
work/resource
driven, rather than time driven; ie I want to enter a fixed amount
of
work,
apply a resource, and then have MSP tell me the resulting duration.
If
the
duration is too long, then I will need to add another resource and so
on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John


:

I have a fixed amount of work to do, so I enter it in the 'work'
field. I
also make sure that my task type is 'fixed work'. I then allocate
2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and
apparently
random
way? Also the 'duration' then adopts one if these random splits,
which
have
no bearing on how long it will take to do the task with two
resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a
work
calendar that is different from the task calendar. Project will
then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear
that
way. It is only software and it responds to a very defined set of
rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10
day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a
fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a
second
resource. Now Project modifies it algorithm slightly. It no longer
holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on
this
task) for a total of 12 hours/day for both resources. Then for the
40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33
days.
If you want the first assignment to change the duration by keeping
work
and unit assignment level fixed, then you will need to re-assign
the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the
duration
will drop to 5 days for 40 hours of work. If you then assign a
second
resource to that task at 100%, Project will further drop the
duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work
and
units then developing and maintaining a plan is a little easier -
at
least in theory

Hope this helps.
John
Project MVP

 

[jonnysaf]

Okay John, 5.00pm enthusiasm got away with me and I thanked you without
trying out the suggestion. Unfortunately the answer doesn't work for me after
all. The reason is that some tasks are already finished by the pause date and
some are yet to be started. MSP (obviously) wont stop or resume a task that
is in the past or in the future, so I cant just 'fill down' as suggested.

Now this might seem pointless (yes, what does it matter that I can't stop a
task that hasn't started), but there are two issues:

1. Some of the tasks are subtasks of rolled up tasks, but it won't insert
the stop resume in the rolled up bar on the Gantt chart.

2. I want to see a continuous vertical line (or gap) on a certain date where
the project pauses and then resumes. This vertical line is linked to another
task which everyone takes part in (it's a document issue, but it could as
well be a training day, a design review, or a team bbq).

Thoughts?

Thanks guys, this is great help!

One more question:

I have to create an event at points 50% and 75% complete. During this
process all work will stop on the main project as all resources will be
directed at the event (a draft document issue).

1. Is it possible to create a 'pause' within all tasks within which this
event can happen?

2. Can I create an event which shows graphically as a vertical task / line?

js

jonnysaf,
It seems like a pretty small focused project if everybody stops what
they are doing to attend/work on the "events". Nonetheless, doing what
you want should be possible. I haven't actually tried this so I'll make
a disclaimer first but take a look at the Stop and Resume fields. It
sounds like you should be able to enter a mass stop date for all tasks
at the first event (enter the date and do a fill-down). When it's over,
do a mass resume date for all tasks. Repeat at the second event.

As far as setting up the two events, I would use the method I described
(or Jack's method if you prefer) for an event milestone at each point.
You can show a vertical line at each event but you will have to draw it
in using the drawing feature of Project, unless you can declare the
Status Date as the event date. In the latter case, go to
Format/Gridlines.

Hope this helps.
John
Project MVP

John, It's all good help!

I have another question: Can I enter a task to start when another task is
75% complete (and always have it at 75%, rather than by date, even when
the
basetask changes its own start or finish due to other constraints)?
Please
dont tell me I need to split the basetask in two...

jonnysaf,
It looks like Jack took this one but let me offer an alternate. I don't
like the concept of task lead since in my mind it borders on prediction
of the future. Yeah I know, just creating a plan requires a certain
amount of prediction but I still don't like the concept of "lead" in a
link.

The following will also work:
[predecessor task]SS + 75%

Hope this helps.
John

js

:

Thanks John,

I can understand your answer (although this method of adjusting the
programme makes the process very long winded, and requires a lot of
adjustment of variables each time I enter a new resource) but I'm
still a
little confused by the way you enter the task; maybe my assumption
of
what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration' for
all
tasks as well as the 'work'. I want to create a program that is
work/resource
driven, rather than time driven; ie I want to enter a fixed amount
of
work,
apply a resource, and then have MSP tell me the resulting duration.
If
the
duration is too long, then I will need to add another resource and so
on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a schedule so
that was my default answer. I think Jan clarified the issue.

John


:

I have a fixed amount of work to do, so I enter it in the 'work'
field. I
also make sure that my task type is 'fixed work'. I then allocate
2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and
apparently
random
way? Also the 'duration' then adopts one if these random splits,
which
have
no bearing on how long it will take to do the task with two
resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources has a
work
calendar that is different from the task calendar. Project will
then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may appear
that
way. It is only software and it responds to a very defined set of
rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a 10
day
[duration] task with 40 hours of fixed work. You assign the first
resource to the task at 100%. Project calculates as follows. For a
fixed
work content over 10 days one resource is only needed half time so
Project adjusts the assignment level to 50%. Then you assign a
second
resource. Now Project modifies it algorithm slightly. It no longer
holds
duration fixed but adds the second resource's work time (assume 8
hr/day) to the first resource's work time (which is 4 hr/day on
this
task) for a total of 12 hours/day for both resources. Then for the
40
hours of fixed work, Project adjusts the duration to 40/12 = 3.33
days.
If you want the first assignment to change the duration by keeping
work
and unit assignment level fixed, then you will need to re-assign
the
first resource a second time. That is, after Project adjusts his
assignment level to 50%, you re-adjust it back to 100% and the
duration
will drop to 5 days for 40 hours of work. If you then assign a
second
resource to that task at 100%, Project will further drop the
duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way it
works. Once you understand how Project calculates duration, work
and
units then developing and maintaining a plan is a little easier -
at
least in theory

Hope this helps.
John
Project MVP

 

[John]

Okay John, 5.00pm enthusiasm got away with me and I thanked you without
trying out the suggestion. Unfortunately the answer doesn't work for me after
all. The reason is that some tasks are already finished by the pause date and
some are yet to be started. MSP (obviously) wont stop or resume a task that
is in the past or in the future, so I cant just 'fill down' as suggested.

Now this might seem pointless (yes, what does it matter that I can't stop a
task that hasn't started), but there are two issues:

1. Some of the tasks are subtasks of rolled up tasks, but it won't insert
the stop resume in the rolled up bar on the Gantt chart.

2. I want to see a continuous vertical line (or gap) on a certain date where
the project pauses and then resumes. This vertical line is linked to another
task which everyone takes part in (it's a document issue, but it could as
well be a training day, a design review, or a team bbq).

Thoughts?

jonnysaf,
I fully appreciate your quick trigger. Unfortunately I'm am often guilty
of ripping out a response and hitting the send button before I've done
all the research. I suppose I could blame it on the sheer number of
posts we respond to but it is really a case of "quick trigger". At least
in the case of my response to your initial post, I did include a
disclaimer.

I finally took a little time to play around with the Stop and Resume
fields. Here are some things I found. When the stop date is entered,
Project automatically updates the % Complete field to be complete
through the stop date. Not necessarily something you want.

You can make stop and resume bars even at a rolled up summary level, but
it requires creating some special bar styles and I'm not sure it is
worth the effort.

I already told you how to create the vertical line at the pause date
(i.e draw it with the drawing tool - it can be attached to any date or
task).

The more I think about it, there probably isn't any quick way to set up
the plan the way you want. The brute force approach is to manually end
all tasks at the event and then create a new set of tasks, as necessary,
when work is to resume. Not convenient but it will work. Another
approach is to force a split on all ongoing tasks at the event date(s).
This could also be done manually but the more efficient approach would
be to use VBA. The VBA procedure could either ask the user for the event
date and then split all on-going tasks or if the event dates and
durations are know ahead of time, it could automatically split all tasks
to effectively insert the "event" gap.

John

Thanks guys, this is great help!

One more question:

I have to create an event at points 50% and 75% complete. During this
process all work will stop on the main project as all resources will be
directed at the event (a draft document issue).

1. Is it possible to create a 'pause' within all tasks within which this
event can happen?

2. Can I create an event which shows graphically as a vertical task /
line?

js

jonnysaf,
It seems like a pretty small focused project if everybody stops what
they are doing to attend/work on the "events". Nonetheless, doing what
you want should be possible. I haven't actually tried this so I'll make
a disclaimer first but take a look at the Stop and Resume fields. It
sounds like you should be able to enter a mass stop date for all tasks
at the first event (enter the date and do a fill-down). When it's over,
do a mass resume date for all tasks. Repeat at the second event.

As far as setting up the two events, I would use the method I described
(or Jack's method if you prefer) for an event milestone at each point.
You can show a vertical line at each event but you will have to draw it
in using the drawing feature of Project, unless you can declare the
Status Date as the event date. In the latter case, go to
Format/Gridlines.

Hope this helps.
John
Project MVP

:

John, It's all good help!

I have another question: Can I enter a task to start when another
task is
75% complete (and always have it at 75%, rather than by date, even
when
the
basetask changes its own start or finish due to other constraints)?
Please
dont tell me I need to split the basetask in two...

jonnysaf,
It looks like Jack took this one but let me offer an alternate. I don't
like the concept of task lead since in my mind it borders on prediction
of the future. Yeah I know, just creating a plan requires a certain
amount of prediction but I still don't like the concept of "lead" in a
link.

The following will also work:
[predecessor task]SS + 75%

Hope this helps.
John

js

:

Thanks John,

I can understand your answer (although this method of adjusting
the
programme makes the process very long winded, and requires a lot
of
adjustment of variables each time I enter a new resource) but I'm
still a
little confused by the way you enter the task; maybe my
assumption
of
what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration'
for
all
tasks as well as the 'work'. I want to create a program that is
work/resource
driven, rather than time driven; ie I want to enter a fixed
amount
of
work,
apply a resource, and then have MSP tell me the resulting
duration.
If
the
duration is too long, then I will need to add another resource
and so
on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a
schedule so
that was my default answer. I think Jan clarified the issue.

John


:


I have a fixed amount of work to do, so I enter it in the
'work'
field. I
also make sure that my task type is 'fixed work'. I then
allocate
2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and
apparently
random
way? Also the 'duration' then adopts one if these random
splits,
which
have
no bearing on how long it will take to do the task with two
resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources
has a
work
calendar that is different from the task calendar. Project will
then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may
appear
that
way. It is only software and it responds to a very defined set
of
rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a
10
day
[duration] task with 40 hours of fixed work. You assign the
first
resource to the task at 100%. Project calculates as follows.
For a
fixed
work content over 10 days one resource is only needed half time
so
Project adjusts the assignment level to 50%. Then you assign a
second
resource. Now Project modifies it algorithm slightly. It no
longer
holds
duration fixed but adds the second resource's work time (assume
8
hr/day) to the first resource's work time (which is 4 hr/day on
this
task) for a total of 12 hours/day for both resources. Then for
the
40
hours of fixed work, Project adjusts the duration to 40/12 =
3.33
days.
If you want the first assignment to change the duration by
keeping
work
and unit assignment level fixed, then you will need to
re-assign
the
first resource a second time. That is, after Project adjusts
his
assignment level to 50%, you re-adjust it back to 100% and the
duration
will drop to 5 days for 40 hours of work. If you then assign a
second
resource to that task at 100%, Project will further drop the
duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way
it
works. Once you understand how Project calculates duration,
work
and
units then developing and maintaining a plan is a little easier
-
at
least in theory

Hope this helps.
John
Project MVP

 

[jonnysaf]

Thanks John,

Glad to see it's not just my dismal lack of knowledge. Time to learn
something about VBA then.

BTW I have been impressed by the speed and quality of the responses I have
got from this forum. Especially given my novice status with a programme so
old that MS dont even provide support for it anymore. It really gives you a
warm fuzzy feeling that there are people out there willing to spend time
sorting out what are probably pretty basic enquiries. Thanks again and
forward this to your boss, supervisor, (or girlfried if you have to explain
the sort dross you deal with on a day to day basis).
A happy customer.

Okay John, 5.00pm enthusiasm got away with me and I thanked you without
trying out the suggestion. Unfortunately the answer doesn't work for me after
all. The reason is that some tasks are already finished by the pause date and
some are yet to be started. MSP (obviously) wont stop or resume a task that
is in the past or in the future, so I cant just 'fill down' as suggested.

Now this might seem pointless (yes, what does it matter that I can't stop a
task that hasn't started), but there are two issues:

1. Some of the tasks are subtasks of rolled up tasks, but it won't insert
the stop resume in the rolled up bar on the Gantt chart.

2. I want to see a continuous vertical line (or gap) on a certain date where
the project pauses and then resumes. This vertical line is linked to another
task which everyone takes part in (it's a document issue, but it could as
well be a training day, a design review, or a team bbq).

Thoughts?

jonnysaf,
I fully appreciate your quick trigger. Unfortunately I'm am often guilty
of ripping out a response and hitting the send button before I've done
all the research. I suppose I could blame it on the sheer number of
posts we respond to but it is really a case of "quick trigger". At least
in the case of my response to your initial post, I did include a
disclaimer.

I finally took a little time to play around with the Stop and Resume
fields. Here are some things I found. When the stop date is entered,
Project automatically updates the % Complete field to be complete
through the stop date. Not necessarily something you want.

You can make stop and resume bars even at a rolled up summary level, but
it requires creating some special bar styles and I'm not sure it is
worth the effort.

I already told you how to create the vertical line at the pause date
(i.e draw it with the drawing tool - it can be attached to any date or
task).

The more I think about it, there probably isn't any quick way to set up
the plan the way you want. The brute force approach is to manually end
all tasks at the event and then create a new set of tasks, as necessary,
when work is to resume. Not convenient but it will work. Another
approach is to force a split on all ongoing tasks at the event date(s).
This could also be done manually but the more efficient approach would
be to use VBA. The VBA procedure could either ask the user for the event
date and then split all on-going tasks or if the event dates and
durations are know ahead of time, it could automatically split all tasks
to effectively insert the "event" gap.

John

Thanks guys, this is great help!

One more question:

I have to create an event at points 50% and 75% complete. During this
process all work will stop on the main project as all resources will be
directed at the event (a draft document issue).

1. Is it possible to create a 'pause' within all tasks within which this
event can happen?

2. Can I create an event which shows graphically as a vertical task /
line?

js

jonnysaf,
It seems like a pretty small focused project if everybody stops what
they are doing to attend/work on the "events". Nonetheless, doing what
you want should be possible. I haven't actually tried this so I'll make
a disclaimer first but take a look at the Stop and Resume fields. It
sounds like you should be able to enter a mass stop date for all tasks
at the first event (enter the date and do a fill-down). When it's over,
do a mass resume date for all tasks. Repeat at the second event.

As far as setting up the two events, I would use the method I described
(or Jack's method if you prefer) for an event milestone at each point.
You can show a vertical line at each event but you will have to draw it
in using the drawing feature of Project, unless you can declare the
Status Date as the event date. In the latter case, go to
Format/Gridlines.

Hope this helps.
John
Project MVP

:

John, It's all good help!

I have another question: Can I enter a task to start when another
task is
75% complete (and always have it at 75%, rather than by date, even
when
the
basetask changes its own start or finish due to other constraints)?
Please
dont tell me I need to split the basetask in two...

jonnysaf,
It looks like Jack took this one but let me offer an alternate. I don't
like the concept of task lead since in my mind it borders on prediction
of the future. Yeah I know, just creating a plan requires a certain
amount of prediction but I still don't like the concept of "lead" in a
link.

The following will also work:
[predecessor task]SS + 75%

Hope this helps.
John

js

:

Thanks John,

I can understand your answer (although this method of adjusting
the
programme makes the process very long winded, and requires a lot
of
adjustment of variables each time I enter a new resource) but I'm
still a
little confused by the way you enter the task; maybe my
assumption
of
what
the programme can acheive is wrong.

From your answer it appears that you have to enter a 'duration'
for
all
tasks as well as the 'work'. I want to create a program that is
work/resource
driven, rather than time driven; ie I want to enter a fixed
amount
of
work,
apply a resource, and then have MSP tell me the resulting
duration.
If
the
duration is too long, then I will need to add another resource
and so
on.

What am I doing wrong?

js

jonnysaf,
Sorry, I always enter an estimated duration when I create a
schedule so
that was my default answer. I think Jan clarified the issue.

John


:


I have a fixed amount of work to do, so I enter it in the
'work'
field. I
also make sure that my task type is 'fixed work'. I then
allocate
2
resources
100% of their time to do the work.

Why does Project 98 split the resources in an uneven and
apparently
random
way? Also the 'duration' then adopts one if these random
splits,
which
have
no bearing on how long it will take to do the task with two
resources
applied
at 100% (ie, one would hope, half of the work time!)

jonnysaf,
One possibility is that one or perhaps both of the resources
has a
work
calendar that is different from the task calendar. Project will
then
only assign the resource during their work time.

Project does not do stuff randomly although sometimes it may
appear
that
way. It is only software and it responds to a very defined set
of
rules
and algorithms when it schedules a plan.

Based on the above let's take an example. Let's say you have a
10
day
[duration] task with 40 hours of fixed work. You assign the
first
resource to the task at 100%. Project calculates as follows.
For a
fixed
work content over 10 days one resource is only needed half time
so
Project adjusts the assignment level to 50%. Then you assign a
second
resource. Now Project modifies it algorithm slightly. It no
longer
holds
duration fixed but adds the second resource's work time (assume
8
hr/day) to the first resource's work time (which is 4 hr/day on
this
task) for a total of 12 hours/day for both resources. Then for
the
40
hours of fixed work, Project adjusts the duration to 40/12 =
3.33
days.
If you want the first assignment to change the duration by
keeping
work
and unit assignment level fixed, then you will need to
re-assign
the
first resource a second time. That is, after Project adjusts
his
assignment level to 50%, you re-adjust it back to 100% and the
duration
will drop to 5 days for 40 hours of work. If you then assign a
second
resource to that task at 100%, Project will further drop the
duration
down to 2.5 days.

This process might seem a little inconsistent but thats the way
it
works. Once you understand how Project calculates duration,
work
and
units then developing and maintaining a plan is a little easier
-
at
least in theory

Hope this helps.
John
Project MVP