Re: Task Hopping
- From: "Steve House" <sjhouse at hotmail dot com>
- Date: Sat, 24 May 2008 08:25:21 -0400
Taks dependencies are not created by sequencing, they are the cause of sequencing. In Project they describe a physical relationship between the tasks such that the timing of the predecessor task either drives or controls the timing of the successor task. Erecting the walls of a building before installing the roof are a FS relationship because Mother Nature doesn't permit us to install the roof in midair and come back later to stuff the walls in underneath it. The time sequence in the schedule is caused by that physical requirement. Project's links model those requirements. While your software developers may jump back and forth between tasks, there surely are some of those dependencies in the Project - you have to write a program module before you can test it, for example. Think not about how they want to sequence their work, instead approach it from the way they HAVE to sequence their work according to the project process itself - if you flowchart the process, diagramming the flow of materials and information through the project from start to end, the result will be a network diagram where each arrow represents a dependency link.
Good planning practices say that EVERY task has at least one predecessor and one successor. IF no other activity is the task's predecessor, the start milestone is. If no other activity is the task's successor, the finish milestone is. There may be multiple pathways between start and finish but every task will lie on at least one of them.
--
Steve House [Project MVP]
MS Project Trainer & Consultant
Visit http://project.mvps.org/faqs.htm for the FAQs
"Sinister" <Sinister@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:42A44722-0492-400A-8617-2017A6602BAE@xxxxxxxxxxxxxxxx
I have a two software developers that want to hammer out a schedule for a
design project they are working on. We have gone through and identified 31
tasks. Each is Fixed work. We have assigned both of them on each task.
Developer 1 puts 75% on every task and Developer 2 puts 50% on every task.
The problem begins when we try to identify the dependencies. According to
them there are none. Their rational is that they go back and forth between
tasks all the time. So, they all start at the same time. Obviously this wont
due considering on the first day Developer 1 has to work 88 hours while
Developer 2 works 72.
So, how do you schedule tasks that a resources bounces around on on any
given day?
Thank you in advance.
.
- Prev by Date: Re: Reports- Soft Copy
- Next by Date: Re: Project can not open the file error
- Previous by thread: Re: Task Hopping
- Next by thread: Re: Task Hopping
- Index(es):
Relevant Pages
|
