checking projects for errors

[andy]

Hi -I am using 2003 and have a plan that has 350 lines, i think its OK but we
have introduced a lot of constraints with start dates..

Is there a way of checking to see if there are additional conflict errors in
the plan.

I am getting some conflict statements but when i check them and press the
"cancel" they go away. if i then close the project without saving and re open
it i dont see the conflict anymore. so i have no idea if the plan is robust

andy

 

[andy]

Hi trevor, i have about 40 tasks that are due to start over a three month
duration that we know the start dates for ( most are reviews which the tasks
feed into). What i cant determine is if my project end date is being hed back
as a result

 

[andy]

Hi trevor,

i have taken on board what you are saying - the restraints for reviews are
to "force" targets to be met either through the need for additional resource
or longer hrs for the tasks leading up to reviews.. If i dont do this then
the resource will take "as long as it takes".. nice try but wrong world!

I have taken all restraints out to allow the project to float with fin
asap(which does reduce my end date.but does make it impractible) so i am in
negotaiton with the resource..
thanks for your offer or a review but the particular project is very
sensitive to allow this to happen

regards

andy

 

[salgud]

Hi trevor, i have about 40 tasks that are due to start over a three month
duration that we know the start dates for ( most are reviews which the tasks
feed into). What i cant determine is if my project end date is being hed back
as a result

It's best to minimize constraints, though sometimes difficult to remove
them entirely. Better to create the schedule so they aren't needed. First,
don't use them just to set dates that someone wants to happen. Most
constraints are there because someone decided arbitrarily that task x needs
to start or finish on date y. Your reviews sound like that kind of thing.
Usually, this is not the case. Occasionally, some outside factor will
determine that a task must occur on a specific date. If you're planning a
St. Patrick's day event, it can't be postponed until the day after!
The most troublesome constraints as far as Critical Path Scheduling goes
are MSO, MFO, SNL, FNL because they force the start or finish date of the
task such that Project can't reschedule them to later dates even when
dependencies demand it. In such a case, you need to attack the Critical
Path (more info on that if you Google this NG) to try to bring the project
back on schedule.
If you're serious about scheduling, it would be well worth your while to
spend a few hours learning CPM and how it is applied by Project. The time
will pay off many times over by enabling you to create meaningful schedules
as opposed to "wish lists". There are a lot of resources, both on and
offline, to do this.
Hope this helps in your world.