RE: project
Hi Lisa
Thank you for your question
A milestone is essentially a point of significance in your project. It could be the completion of a significant task, a point at which a payment is made or received, or even just an arbitary point created by management to monitor progress on the project.
Milestones should always be set for the start and completion of a project, with all tasks linking through to them. Tasks with no natural successor tasks should link to the finish milestone. Tasks with no natural predecessors should have the start milestone link through to them.This helps ensure scheduling continuity
Finally, if your project has tasks that are driven by external events over which you have no control then you could mark them with a milestone. For example if a phase of your project cannot start until the client has released some information to you, then you could mark this release point as a milestone, and link it to the relevant task in your project. You could then use the "late finish" to identify the latest date by which this information must be released, before the completion of the project is delayed.
Hope this helps
Regards
Stephen