Guild of Project Controls: Compendium | Roles | Assessment | Certifications | Membership

Tips on using this forum..

(1) Explain your problem, don't simply post "This isn't working". What were you doing when you faced the problem? What have you tried to resolve - did you look for a solution using "Search" ? Has it happened just once or several times?

(2) It's also good to get feedback when a solution is found, return to the original post to explain how it was resolved so that more people can also use the results.

Tasks to Milestones

1 reply [Last post]
lyonel scapino
User offline. Last seen 6 years 46 weeks ago. Offline
Joined: 30 May 2017
Posts: 2
Groups: None

I have a task with a milestones at the end of it in an existing MS Project. The successor is linked to the milestones itself and has a lead time. It is a finish to finish link. But the lead time should still be on the predecessor task? or on the milestone itself? 

Given that it is a finish to finish relation it should be the milestone or the task that is considered as the predecessor?

Or should it always be the task that is the predecessor?

Isn t linking to a milestones going to cause trouble for future MS Project calculations and/or optimizations?

Many thanks

Replies

Tom Boyle
User offline. Last seen 3 weeks 3 days ago. Offline
Joined: 28 Nov 2006
Posts: 304
Groups: None

lyonel,

I am sorry that after reading your question 3 times, I still don't understand it.  Please re-phrase.

Between any arbitrary task and an arbitrary milestone (i.e. a zero-duration task), Project allows one of four relationship types and any amount of positive or negative lag.  ("Lead" in this context means negative lag.)  Which to chose depends on the real-world restraints you are trying to model.  There is no arbitrary solution.  As a rule linking to and from milestones causes no problems in Project's calculations.