Task Constraints-which ones are really not that usable?

[anovak]

Folks,

Over the last few years, I've either used the default "As Soon As
Possible" or "Start No Earlier Than" constraints. We are an IT shop
and and I can't quickly think of common situations that would require
any of the other constraints.

There is a "newbie" here in the department who has become infatuated
with "Finish No Later Than" type of constraints - I think as an
alternative to taking baselines, entering deadlines, and comparing
baselines with actuals moving forward. It seems to me that its
dangerous to rely so heavily on constraints to "manage" your schedule.

Could someone please comment on the other task constraints and go into
why you should shy away from and why? Or if there are practical uses
for them - and in which cases?

Thanks,
Andy Novak
UNT

 

[Rod Gill]

For normal scheduling purposes, adding constraints is very
counter-productive, firstly because the critical path becomes meaningless,
secondly because you lose flexibility and the ability for the schedule to
re-calculate automatically in response to changes.

If a task has a constraint (EG a resource is not available until a specific
date, a meeting happens then Etc.) I advocate having a summary task near the
top of the schedule called Constraints. Under it I have milestones that
represent all date constraints for the schedule with a note on each one to
explain why the constraint is there. All other tasks that are affected by a
constraint are then linked directly or indirectly to it. This way management
can see exactly what constraints they need to manage/modify to effect a
quicker finish.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com

 

[anovak]

For normal scheduling purposes, adding constraints is very
counter-productive, firstly because the critical path becomes meaningless,
secondly because you lose flexibility and the ability for the schedule to
re-calculate automatically in response to changes.

If a task has a constraint (EG a resource is not available until a specific
date, a meeting happens then Etc.) I advocate having a summary task near the
top of the schedule called Constraints. Under it I have milestones that
represent all date constraints for the schedule with a note on each one to
explain why the constraint is there. All other tasks that are affected by a
constraint are then linked directly or indirectly to it. This way management
can see exactly what constraints they need to manage/modify to effect a
quicker finish.

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:http://www.projectvbabook.com

Thanks Rod. Your first paragraph especially helped. I'm trying to
get everyone to focus on the basics first.

 

[Rod Gill]

Good Luck!

--

Rod Gill
Microsoft MVP for Project

Author of the only book on Project VBA, see:
http://www.projectvbabook.com