Re: Task Start Dates
- From: "Jan De Messemaeker" <jandemes at prom hyphen ade dot be>
- Date: Thu, 9 Feb 2006 15:01:15 +0100
Hi Trevor and all,
I LOVE this explanation as much as I DISLIKE negative lag. :-)
--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
http://users.online.be/prom-ade/
+32-495-300 620
"Trevor Rabey" <trabey@xxxxxxxxxxxxxxxxxxxxx> schreef in bericht
news:43eb30a7@xxxxxxxxxxxxxxxxxxx
I hate to split hairs, but I think that's not quite what it means, withoutwould
qualification, and the exact meaning can be important.
It means, that:
if we are scheduling forwards iaw with good Critical Path Method (you
have to like pain to do anything else)edays
and if there are no date constraints to consider on either Task (Task
Properties, Constraint Type and Date)
and if both Tasks use the same Calendar and there are no other Calendar
considerations (eg Resource Calendars, Working Time)
and bearing in mind that we are talking about working days rather than
and if there is no progress recorded in Actuals along with Tasks havingbeen
re-scheduled and perhaps split, depending on calculation options,also
and if there are no other Predecessor Links with other Tasks
and if there is no Resource Leveling involved
.. and we may as well throw in Task Type and effort driven as a
consideration except that it would seem to be the only thing that doesn't
have to be kept in mind here because it can only affect duration which
doesn't come into this case.NO
Then Task 101 will be scheduled to start as soon as possible (Day 1), but
SOONER than 10 days before Task 100 starts, because, according to what youlaw
have put into your model, it can't (due to something immutable like the
of gravity). So it means don't expect to be able to do it sooner than thisall
(and if it is on the critical path make sure you do it no later).
When you actually come to do it the condition may not be so strict after
and you can do it sooner, and choose to or not, or other events notmodeled
may prevent it from happening that soon anyway.software
However, after all this arduous thinking, unless start of Task 100 is a
fixed Date (like the opening ceremony of the olympic games or a solar
eclipse) in which case Task 101 is also a fixed Date, we have a situation
where the "trigger" event for Task 101 is in its own future. Since you can
never know for sure when you are at 10 days sooner than the start of Task
100 until after it has happened, Task 101 can never be started. The
let's you plan it even though it can't be executed. Suggest sticking withFS
Links and positive lag.
"Rick Roszko" <RickRoszko@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ADD63287-394C-4D92-8A56-B2F46D9C44A5@xxxxxxxxxxxxxxxx
By 2 weeks you mean 10 business days I assume?
Let's say you have task 100 and task 101
In predecessors for the second task (101), put in 100SS-10d
which means task 100 will start 10 days befor task 100 starts
--
Rick Roszko
PM, MSPS, Network Consultant
"Diane" wrote:
How do I create a start date that is 2 weeks prior to another task?
.
- References:
- Re: Task Start Dates
- From: Trevor Rabey
- Re: Task Start Dates
- Prev by Date: Re: Resource Pool and Consolidated Project file corruption - how to prevent it?
- Next by Date: Re: Task Start Dates
- Previous by thread: Re: Task Start Dates
- Next by thread: Re: Task Start Dates
- Index(es):
Relevant Pages
|