Hi Charlene,
I would just add that you would be better advised to use a Deadline Date (in
Task Information/Advanced tab) rather than Must Start On. That will allow
the meeting date to wander depending on the predecessor changes. Project
will then give you an Indicator if the deadline is overrun by the plan,
allowing you to concentrate on its predecessors to bring the schedule back
into line.
FAQs, companion products and other useful Project information can be seen at
this web address:
http://project.mvps.org/faqs.htm
Hope this helps - please let us know how you get on
Mike Glen
MS Project MVP
See
http://tinyurl.com/2xbhc for my free Project Tutorials
Thanks Jim, I will try again with these constraints... however, I believe
I
was utilizing these parameters and still was not able to have tasks listed
beneath the "fixed date" tasks load up into all available resource space.
In this case, the resources (people) are being schedule to review jobs and
in some cases, their visits to certain sites need to align with other
people/etc and therefore have specific dates. I would like to link the
jobs,
because if I add a new task into the schedule, I need the functionality
that
the other tasks will adjust accordingly. The goal is to create a work
schedule, that optimizes their time, and is flexible to adjust to new
tasks
(while respecting fixed timelines).
It is not feasible for me to list each task in chronological order, since
that is a large part of what I need to software to do for me. ( many
tasks,
many people)
Thanks again
Charlene
Project will respect any constraints and let other tasks fill in as
you describe. If you have a fixed meeting for example, mark that as
"Must Start On". It will not move. The danger with such constraints
is if that meeting has any predecessor tasks (e.g., prepare briefing),
Project will give you errors if there is not enough time to prepare
the briefing. Initially you would NOT have the constraint on the
meeting and let Project put it where it wants to based on the
predecessor links. Then you call the rest of the people going to the
meeting, compare everyone else's schedules, and pick a firm date.
When you finally get a suitable time nailed down, then you should set
the MSO constraint. After that, cross your fingers that you get all
the predecessor work completed!
You should strive to use links as much as possible rather than
constraints. (Be aware that manually entering a date in the Start or
Finish column will set a constraint, as Jim mentioned.) Project will
fill in the gaps if possible. By default, the entire task must fit
within the gap, but you can set priorities on tasks and have the
leveling logic interrupt (split) a lower priority task for a resource
to switch to a higher priority task. Check out the options on the
leveling tab for global settings. You can also mark a particular task
as "do not split" if needed.
The beauty of the schedule when set up this way is that things shift
"properly" when some tasks take longer or shorter than originally
planned. What-if scenarios are easier to explore. You'll soon see
that some tasks are more important to complete on time than others
(i.e., the "critical" tasks).
Paul