• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint
Share this Page URL
Help

Hour 5. Turning the Task List into a Sch... > Resolving Conflicts Caused by Constr...

Resolving Conflicts Caused by Constraints

If you decide to go ahead with a change that creates a scheduling conflict, then you must deal with the conflict resulting from the constraint. When a scheduling conflict occurs, Project has to honor the link to the predecessor (and schedule the constrained task past its constraint date), or it has to honor the constraint and not observe the link to the predecessor. By default, Project honors constraint barriers at all times and ignores the link instructions because constraints are normally what we call "hard" constraints.

With hard constraints, the screen really doesn't tell you for certain that a scheduling conflict exists. The link arrow doubles back on itself in a tortured S-shape (see Figure 5.12). However, this could just as well be the link arrow for a Finish-to-Start link with lead time. The indicator is just the same as it is for all inflexible constraints, so you can't tell that there's a scheduling conflict just from looking at the screen. Furthermore, you have seen the last warning from the Planning Wizard. You're on your own if you want to find the conflict and fix it.


PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint