If you look at the filter that defines a slipping task, it doesn't look at
start dates at all. The filter checks to see if a: the task hasn't yet
finished, b: it has been baselined, and c: the expected finish is later than
the original baseline finish. If the current date is past it's scheduled
start date and you have no actuals posted, MSP doesn't know if the task
didn't start on time or you just haven't gotten caught up on your data
entry. Using the "Reschedule uncompleted work to start after" would push
the finish date out to what you'll hit if you start the late task now, but
you've screwed that up by using a "Start No Later Than" constraint which
instructs Project NEVER to schedule it later no matter what. Hard
constraints like that can be disaster in a plan and should only be used when
you simply have no alternative.
Steve House
MS Project MVP
confused said:
If I have set a 'Start No Later Than' constraint on a task, and the
current date is past that SNTL date, why does the task not show up on the
'Slipping Task' report?
