Total Slack Calculation

[Blueglass]

What's the proper reply to managers that can't believe that MS Project is
calculating total slack correctly?
The folks I'm working with add negative lag, Start to Start Constraint
types, Finish to Finish Constraint types and then say, "I can't believe we
have negative slack."

 

[John]

What's the proper reply to managers that can't believe that MS Project is
calculating total slack correctly?
The folks I'm working with add negative lag, Start to Start Constraint
types, Finish to Finish Constraint types and then say, "I can't believe we
have negative slack."

Blueglass,
I guess the best starting point is to ask your managers WHY they believe
Project is not calculating total slack correctly. Get an example and
then maybe we can help disseminate their misconceptions.

I find that some users/managers have some preconceived notions on how
scheduling should work. Sometimes those notions don't fit with Project's
scheduling algorithms so they think Project is doing it incorrectly.
Most of the time, (but not all), it is a lack of understanding by the
user - hence we get questions to answer.

John
Project MVP

 

[Blueglass]

Thanks for the input! Yes, I'm spending too much time removing the lags and
the constraints and producing PERT charts using another software to
demonstrate to them that MS Project is doing it's job correctly. Frustrating!

 

[John]

Thanks for the input! Yes, I'm spending too much time removing the lags and
the constraints and producing PERT charts using another software to
demonstrate to them that MS Project is doing it's job correctly.
Frustrating!

Bluegrass,
It sounds like your managers don't have that firm a grasp on what a
dynamic schedule should do and in particular, how Project can help. By
making you "force" the schedule, your time is wasted, the application
(Project) is underutilized and end product (i.e. viable dynamic
schedule) is questionable.

Nonetheless, you're welcome and good luck with your arguments.

John
Project MVP