Re: Why it is better to not use Deadline dates
- From: "Jan De Messemaeker" <jandemes at prom hyphen ade dot be>
- Date: Wed, 30 Nov 2005 21:16:18 +0100
Hi Michele,
I forgot you are a fan of "As Late As Possible", something which in my
opinion does not work properly in Project, and I definitely will never use
schedule from finish date.
So I'm not arguing in that kind of world.
Project calculates late dates as well as early dates without me having to
use these constraints.
Sorry to have made you lose some time.
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
+32-495-300 620
"Michele" <Michele@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:42737055-2823-471B-96BA-3474063DD8EE@xxxxxxxxxxxxxxxx
> Hi Jan,
> Really thank you for reading me.
> When you say that deadlines do not directly influence the schedule I can't
> agree with you and to prove my reasons I suggest you to do the next tests:
> Test 1
>
> 1) Create a new project scheduled from a start date, let's assume that the
> start date of the project is set to be 27/11/05 and then create three
tasks,
> called a, b, c.
> 2) Give the three tasks a duration of 1 day.
> 3) Link a and b (a as a predecessor of b) with Finish-to-Start relation
with
> 2 days of positive lag.
> 4) The three tasks have the defaulted constraint "As soon as possible".
> 5) Now you have the critical chain of the project, made of the two tasks a
> and b, and MS Project calculated consequently the finish date of the
project
> that is 01/12/05.
> 6) Associate to task c a deadline date equal to 05/12/05 and then change
the
> constraint of task c into "As late as possible"
> 7) You will see that MS project will still wrongly indicate you that the
> finish date of the project (In project information) is 01/12/05 and
> consequently it will still indicate you that task a and b are critical,
while
> they should have both an amount of total slack equal to 1 day since the
task
> c is the only one task that determines the finish date of the project,
that
> is 05/12/05.
> 8) If, instead of associating to task c a deadline date, you create a
> milestone d with 0 days of duration, you associate it a "Must start on"
> constraint with a constraint date equal to 06/12/05 and you link to
milestone
> d the task c(c as a predecessor of d with 0 days of lag) leaving the
> constraint of c equal to As late as possible you will see the correct
> situation, that is a and b are not anymore critical and both have an
amount
> of total slack equal to 1 day and milestone d and c are both critical like
> the way they should correctly be.
> Test 2
>
> 1) Create a new project scheduled from a finish date, let's assume that
the
> finish date of the project is set to be 02/12/05 and then create three
tasks,
> called a, b, c.
> 2) Give the three tasks a duration of 1 day.
> 3) Link a and b (a as a predecessor of b) with Finish-to-Start relation
with
> 2 days of positive lag.
> 4) The three tasks have the defaulted constraint "As late as possible".
> 5) Now you have the critical chain of the project, made of the two tasks a
> and b, and MS Project calculated consequently the start date of the
project
> that is 29/11/05.
> 6) Associate to task c a deadline date equal to 30/11/05 and leave the
> constraint of task c equal to "As late as possible", Ms project correctly
> schedules task c to start 30/11/05 and finish 30/11/05.
> 7) Associate to task c an actual start date equal to the current scheduled
> start date, that is 30/11/05(with 0% of actual work), you will see that MS
> project will wrongly make finish the task c on 01/12/05 and it will
> consequently indicate you that task c finishes on 01/12/05 which is later
> than its deadline on 30/11/05. So ,as you see, in this case the deadline
date
> does affects the schedule of task c, and that is proved by the fact that,
if
> you clear the deadline date of c, the schedule of c returns the one you
had
> at the beginning.
> 8) If, instead of associating to task c a deadline date, you create a
> milestone d with 0 days of duration, you associate it a "Must start on"
> constraint with a constraint date equal to 01/12/05 and you link to
milestone
> d the task c(c as a predecessor of d with 0 days of lag) leaving the
> constraint of c equal to As late as possible(and clearing its actual start
> date) you will see the correct situation that is task c starting 30/11/05
and
> finishing 30/11/05 even if, then, I associate to task c an actual start
date
> equal to the current scheduled start date, that is 30/11/05(with 0% of
actual
> work), it will still correctly finish on 30/11/05.
>
> I hope to have been enough clear.
> Thank you Jan.
> Best regards
> Michele
>
>
>
>
> "Jan De Messemaeker" ha scritto:
>
> > Hi Michele,
> >
> > While I too am a user of your "deadline method through milestones" I
can't
> > think of an instance (at least when scheduling from Project start, which
I
> > always always do) where the use of a "deadline" may be harmful,
especially
> > because deadlines do not directly influence the schedule.
> >
> > HTH
> >
> > --
> > Jan De Messemaeker
> > Microsoft Project Most Valuable Professional
> > http://users.online.be/prom-ade/
> > +32-495-300 620
> > "Michele" <Michele@xxxxxxxxxxxxxxxxxxxxxxxxx> schreef in bericht
> > news:BE24537A-3153-472E-802A-1E911D8B13C9@xxxxxxxxxxxxxxxx
> > > I forgot to write that the milestone task must have a constraint equal
to
> > > "Must start on" and the constraint date must be the deadline date one
> > wants
> > > to associate to a task.
> > > Best regard
> > > Michele
> > >
> > > "Michele" ha scritto:
> > >
> > > > As greatly suggested to me by John Jensen I found a work around to
> > achieve my
> > > > objective in scheduling a project using MS project.
> > > > While I am convinced that the engine of MS project software is
working
> > fine
> > > > regarding the backward pass and forward pass, I am convinced, on the
> > > > opposite, that associating a deadline date to a task MAY have(ONLY
IN
> > CERTAIN
> > > > SPECIFIC CASES) bad consequences on the engine of Project, causing
> > illogical
> > > > and not correct results.
> > > > For anyone who was interested in knowing which are the cases I
describe
> > > > above I am helpful to write him/her.(Anyway they are mostly related
to
> > the
> > > > tracking of the tasks)
> > > > The work around I found about avoiding to use deadline dates is to
> > > > create(one for each task one wants to associate a deadline date,
clearly
> > only
> > > > if the deadline dates are different)a milestone task(With 0 days of
> > duration)
> > > > and link the task u want to associate a deadline date to the
milestone
> > task
> > > > with Finish-to-Start relation.
> > > > In this way all work fine, even and especially when the planner
starts
> > > > tracking that task.
> > > > I hope that this advice can be helpful to anyone of you.
> > > > Best regards
> > > > Michele
> > > >
> >
> >
> >
.
- Prev by Date: Re: bibliography
- Next by Date: Re: Why it is better to not use Deadline dates
- Previous by thread: Re: Why it is better to not use Deadline dates
- Next by thread: Re: Project- allow me to choose how planned overtime affects duration
- Index(es):
Relevant Pages
|
Loading
