How to deal wtih launch date

[jpas1954]

I am working with a client whose scheduled product release is Dec. 2010 and
am attempting to keep the schedule as dynamic as possible. In speaking to
marketing, they advise me that they can apply for a trademark no sooner than
three years before the release date. I *could* put in a "Apply for trademark"
activity and put a hard constraint that says, "Start no sooner than Dec.
2007". But again, that's not dynamic and I want that task to slip if other
tasks slip. Is there a good way to detail this?

 

[John]

I am working with a client whose scheduled product release is Dec. 2010 and
am attempting to keep the schedule as dynamic as possible. In speaking to
marketing, they advise me that they can apply for a trademark no sooner than
three years before the release date. I *could* put in a "Apply for trademark"
activity and put a hard constraint that says, "Start no sooner than Dec.
2007". But again, that's not dynamic and I want that task to slip if other
tasks slip. Is there a good way to detail this?

jpas1954,
From your description, the only link for the trademark is 3 years before
the product release. It has no other predecessors and therefore it
should only "float" with the release date. That is not an unusual
scenario. In my industry, we often encountered things like, "submit test
plan to customer xx days prior to start of test".

There are various ways to handle that linkage. One is to use a
start-to-finish link with a lead of, in your case, 3 years. For example
let's say the release date task ID is 400. For a 3 year lead the
predecessor on the trademark task would be: 400SF-1095 edays. Note: the
exact number of days may need some adjustment to get exactly 3 years but
you get the idea.

With the above structure, the trademark task will by dynamic with the
release date.

Hope this helps.
John
Project MVP

 

[jpas1954]

Great answer. Thanks. Works like a charm.

jpas1954,
From your description, the only link for the trademark is 3 years before
the product release. It has no other predecessors and therefore it
should only "float" with the release date. That is not an unusual
scenario. In my industry, we often encountered things like, "submit test
plan to customer xx days prior to start of test".

There are various ways to handle that linkage. One is to use a
start-to-finish link with a lead of, in your case, 3 years. For example
let's say the release date task ID is 400. For a 3 year lead the
predecessor on the trademark task would be: 400SF-1095 edays. Note: the
exact number of days may need some adjustment to get exactly 3 years but
you get the idea.

With the above structure, the trademark task will by dynamic with the
release date.

Hope this helps.
John
Project MVP