Dependencies

E

Elsa

Hi,
I am aware that creating dependencies using summary tasks can lead us to
lots of trouble (circular dependencies). I was wondering what is the best
practice when I have the following situation:
Summary task A
A.1
A.2
A.3
Milestone end of A
Summary task B
B.1
B.2
Milestone end of B

There is no dependency between substasks, A.1, A.2 or A.3 they are done in
paralelle and no dependencies between B.1 and B.2) but I want to create a
dependency between group A and its milestone (end of A) and I also want a
dependency that state that group B should begin after group A is finnished.

Could anyone guide me to the best dependency scheme I should use in this
situation, please?
 
D

Dave

I would probably have a start milestone for both groups A and B. That
would certainly give you the ability to link group A to B FS. Then the
start milestone for each group drives the start of the tasks in each group.

It also makes it slightly easy to reschedule work as you can just move
the start milestone if work has not started on a given group.
 
E

Elsa

Thanks a lot for your sugestion. And would you include the new milestones
(start milestone A and B) in the corresponding Summary task or outside it?
 
D

Dave

I personally would put the new milestones under the summary task so that
if you move them (and hence the whole group), the summary task moves
with them.
 
E

Elsa

Thanks Dave! :)
Elsa


Dave said:
I personally would put the new milestones under the summary task so that
if you move them (and hence the whole group), the summary task moves
with them.
 
M

Mike Glen

Hi Elsa,

I would also link the start milestones to their respective tasks and ditto
for the finish milestones, then this would become completely flexible and
avoid typing in any dates (which cause constraints)

Mike Glen
MS Project MVP
See http://tinyurl.com/2xbhc for Project Tutorials
 
S

Steve House

Adding to other advice, I teach my classes that projects should have at
least a start milestone and an end milestone. Within the project, ALL
activities must have at least one predecessor and at least one successor.
If no other task is a task's predecessor, the start milestone is it's
predecessor. If not other task is a task's successor, the end milestone is
the successor. All possible sequences through the project begin with the
start milestone and end with the end milestone and there's one and only one
end date, there are no dangling chains with independent endings.
 
E

Elsa

Thank you very much for your advice Steve!
Elsa


Steve House said:
Adding to other advice, I teach my classes that projects should have at
least a start milestone and an end milestone. Within the project, ALL
activities must have at least one predecessor and at least one successor.
If no other task is a task's predecessor, the start milestone is it's
predecessor. If not other task is a task's successor, the end milestone is
the successor. All possible sequences through the project begin with the
start milestone and end with the end milestone and there's one and only one
end date, there are no dangling chains with independent endings.
 
N

Naomin

On a related issue, if A1, A2 and A3 are simultaneous ("parallel") and they
end at unpredicatable times, would the predecessor for the A milestone finish
be all 3 A lines?
thanks,
Naomi
 
N

Naomin

I suppose I'm describing the Actual Finish. That is, as life is,
unpredictable. Ultimately my finish milestone will be predecessed by the
latest of the 3 parallel tasks. Correct?
 
M

Mike Glen

Yes, as long as they have no constraints, ie they are all As Soon As
Possible.

Mike Glen
Project MVP
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top