Re: External timeline dependencies
- From: John <mjensen@xxxxxxxxxxxx>
- Date: Mon, 08 Sep 2008 20:02:03 -0700
In article <F5308532-D927-4E73-A365-3F771547FC21@xxxxxxxxxxxxx>,
Jen B <Jen B@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
I am using Project 2003 enterprise. I have 3 plans linked together, a
resource plan, vendor submitted plan, and master plan. However, it is not
appropriate to link to the vendor plan for submission to management. How do
I reflect the durations they expect and the review/revise cycles that belong
to our staff?
For example; they will write a guide and expect it to take 2 weeks, my staff
must review that guide within 5 days. How do I create a task for our review
designed to start at the end of the estimated 2 weeks without linking but
still showing a 2 weeks and 5 days timeline.
Jen,
Why is it "not appropriate" to link a vendor plan into your plan "for
submission to management"? Not wanting to provide vendor information to
another contractor or to an end use customer I can understand, but
"management" is part of your company and your management should be aware
of a vendor they have hired.
Nonetheless, if linking the plans together is forbidden they your only
real choice is to create a milestone that is entered manually to
represent the vendor's completion of the "guide".
Hope this helps.
John
Project MVP
.
- References:
- External timeline dependencies
- From: Jen B
- External timeline dependencies
- Prev by Date: Importing labour from CSV / XLS into Project 2007
- Next by Date: Re: Resource Capacity
- Previous by thread: External timeline dependencies
- Next by thread: RE: External timeline dependencies
- Index(es):
Relevant Pages
|
