Tasks Dependencies - Very Important Question

[Rami]

Hi

As you know, you can create a relationship between tasks, like
Finish-To-Start.

And as the name suggests, the next task should not start until the previous
finishes. But in Project Server, the resource can start that Successor task
without having the Predecessor task finished.

I am really astonished how Primavera stops you from doing such thing but Ms
Project does not!!

Thanks

 

[Brian Kennemer]

Hi

As you know, you can create a relationship between tasks, like
Finish-To-Start.

And as the name suggests, the next task should not start until the
previous finishes. But in Project Server, the resource can start that
Successor task without having the Predecessor task finished.

I am really astonished how Primavera stops you from doing such thing
but Ms Project does not!!

Thanks

I too am astonished that Primavera would actually stop a resource from
doing work.

The way I have always looked at it is that if the resource can do the
work before the predecessor is complete then the link was wrong in the
first place. Also, if this kind of thing is happening it points to a
communication issue. If in fact the resource should not work on a task
then the PM should have been talking to them about this. By the time
the timesheet application in use (Project Server or Primavera) comes
into the picture it is too late. The "work" is already at least partly
done. The fact that Primavera stops them from entering their work into
the timesheet does not really DO anything. They have already done it.

 

[Rami]

Brian

you convinced me

Hi

As you know, you can create a relationship between tasks, like
Finish-To-Start.

And as the name suggests, the next task should not start until the
previous finishes. But in Project Server, the resource can start that
Successor task without having the Predecessor task finished.

I am really astonished how Primavera stops you from doing such thing
but Ms Project does not!!

Thanks

I too am astonished that Primavera would actually stop a resource from
doing work.

The way I have always looked at it is that if the resource can do the
work before the predecessor is complete then the link was wrong in the
first place. Also, if this kind of thing is happening it points to a
communication issue. If in fact the resource should not work on a task
then the PM should have been talking to them about this. By the time
the timesheet application in use (Project Server or Primavera) comes
into the picture it is too late. The "work" is already at least partly
done. The fact that Primavera stops them from entering their work into
the timesheet does not really DO anything. They have already done it.

--

Brian Kennemer
microsoft consulting services
brian[period]kennemer[the "at" symbol]microsoft[period]com