JRT said:
Hello,
New to Project, but am trying desparately to learn it on my own.. ha ha..
I have a question, I am putting together a huge schedule that requires
information to be done at least 120 days prior to the main task.
Questions:
Can I use that main task and work backwards and if so, how do I put in for
something to start 120 prior to that?
Thanks
Janet
Janet,
First of all congratulations for having the gumption to learn Project on
your own. However, you are probably finding that a self-taught approach
is very frustrating because Project has a steep learning curve. May I
suggest that you take a look at a couple of things that might help with
the learning curve, both on our MVP website. First go to:
http://www.mvps.org/project/links.htm
and find the link for fellow MVP, Mike Glen's series on "basic Project
lessons and techniques". You can also find a bunch of helpful
information at:
http://www.mvps.org/project/faqs.htm
With regard to your specific question. There are several ways to handle
early tasks - it depends on a lot of factors. One viewpoint says that if
there are early tasks, then that's when the project really starts, so
they are not really early. You might want to try that approach. For
example, let's say that there is a specification review that spans a
duration of 30 days and needs to be completed 120 days prior to contract
award. You might simply set the Project Start Date (found under
Project/Project Information) to the start date of the spec review. Then
use a simple start-to-start link with a delay of 120 days for the
contract milestone, which is the starting point for all other tasks in
the project.
Other approaches include using a finish-to-start with a 120 day lead
link between the contract milestone and the "early task", fixing the
contract milestone with no link to the "early task", not including the
early task at all (maybe it is company funded and not part of the
contractually funded project), etc.
Hope this helps.
John
Project MVP