effects of early completion of tasks

L

lynne baker

Hi
We're running project server 2002 and project pro 2002 and PWA
Further to the issue of tasks finishing earlier than anticipated, we
now have the problem that the dates of successor tasks move forward,
which we don't want.
Ideally we would like the successor tasks to stay where they are, and
for the free time to be allocated elsewhere.
We are tracking the fact that tasks have finished earlier by entering
100% and remaining hours to 0.
Is there a way to prevent successor task dates from moving forward?
The problem is that it makes resource issues elsewhere!
Any help is greatly appreciated
Many thanks
lynne
 
E

Eric

I had the same problem. Look at the successors constraint.
I bet you have it to start as soon as possible, change the
constraint to one that fits, usually I do start no earlier
than or whichever one. Hope this helps
Eric
 
D

Dale Howard

Lynne --

I disagree with Eric's suggestion to place constraints on successor tasks,
as I think you will find it to be way too much work setting SNET constraints
on every task. In your situation, I believe what you want to do is to
"reserve" the entire Duration of each task, even if the work finishes early,
so that successor tasks start when scheduled (and not earlier). In a
situation like this, I would recommend the use of Fixed Duration task types
for each of your tasks. I believe this will accomplish what you desire to
do, and will be much easier to do.

To set the task type for every task in your project, complete the following
steps:

1. Click the Select All button in the upper left corner of the task sheet
2. Click the Task Information button on the Standard toolbar
3. Click the Advanced tab
4. Set the Task Type value to Fixed Duration
5. Click the OK button

When you use Fixed Duration as the task type, and the Work on a task
finishes early, Microsoft Project will show this early finish with a task
split indicator (....) at the end of the Gantt bar. Some people "freak out"
when they see the split indicator, so be prepared. Hope this helps.
 
J

Jon

Dale,

Are you suggesting that we set all tasks to Fixed Duration
if they have successors?
Thanks
Jon
 
D

Dale Howard

Jon --

No, I am suggesting that Lynne set tasks in her project to Fixed Duration,
given the need that she describes in her original message. As far as
whether you should do that in your own projects depends whether you have a
situation like she does. Please reread her original message, and then tell
me if you have a situation like this, too.
 
S

Steve House

I disagree with Dale's approach. Remember the driving force is the most
efficient project schedule that will allow you to finish your project at the
earliest possible date. If I finish Task X a week earlier than originally
planned, wouldn't it make more sense to go ahead and start on its successor
as soon as possible so I could take advantage of the improved efficiency of
my project team and either bring the whole project in ahead of plan or
retain that extra duration as a cushion in the time bank to help absorb any
future problems caused by something subsequently running late? If your
problem is the advancing schedule causes a resource overallocation down the
line, resource leveling the affected tasks will fix that.

Another simple way to keep the downline schedule from changing if you're
sure you want to do that is, after posting the actual, to add in how ever
much lag time is required in the link from the early finishing task to its
successor that will be required to keep the successor starting as originally
planned.
 
Top