If you don't use resource levelling links are the only way to establish the
sequencing (well, you could use SNET constraints but that opens up an even
bigger can of worms). But why are you opposed to levelling? In your sample
scenario it is the ideal solution, a perfectly normal practice, and only
involves a few mouse clicks. I'd have "Start" as a milestone and link it as
a predecessor to all 4 tasks. Since there is no obligatory sequence none of
the tasks would be linked to each other. If there is a preferred sequence,
descending Task Priorities would be assigned with the highest priority going
to the task you prefer to be done first, next lower to the task to be done
next, and so forth. Since there is a 2 day delay on the fixture due to its
repair, I'd put a SNET constraint on the "Install Fixture" task of the date
it's promised to get back to your site from being repaired - can't start its
installation until its delivered. All 4 tasks link in turn to the "Finish"
milestone resulting in 4 parallel chains of start->action task->finish in
your project. Assign your resource and resource level. You're done, a
nicely sequenced and flexible plan. If something changes after work starts,
like you had paint before trim but the resource started trim first anyway,
all you need do is enter actual work on the tasks when it was actually done
and do a "Reschedule Uncompleted Work To After [status date]" and everything
gets updated and resequenced properly.
Of course, since you don't have to either a) coordinate the activities of a
set of different resources with different skills; or b) micromanage your
resource's workday; you could just coalesce all 4 tasks into 1 task "Redo
Bathroom" with a duration of 20 days and let the resource organize his own
work approach - he should be perfectly capable of doing that without your
having to hand-hold him through the process telling what order to do the
various components.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit
http://project.mvps.org/faqs.htm for the FAQs