B
Brian Lukanic
Scenario:
Master 1 (Saved often by PM1. NEVER published.)
SubA (Saved and published ONLY by PM1. Stays checked out.)
SubB ""
SubC ""
SubD ""
SubE ""
Master 2 (Saved and published by PM2.)
SubA (PM2 is not allowed to touch SubA's tasks. He is allowed to only
insert it as read-only in their master. PM1 does all of the updating of SubA)
Can you please validate my assumptions:
1. This scenario is allowed by Server 2007
2. Any time they open Master2, PM2 will see changes made to SubA by PM1.
(perhaps not by an alert window that appears when changes are made in
cross-project dependencies, but if they have a discerning eye they would see
new dates as well as new tasks in the sub.)
3. When PM2 saves or publishes Master2, they will get an alert that says,
"SubA is a sub in another project and may be published. This might cause
problems when publishing." Although this alert pops up, PM2 is safe because
he never made any changes to SubA, AND because PM1 never published Master1.
When PM2 publishes Master2, there is no risk of "double-publishing" SubA's
assignments, etc. But Master2 will be able to be published.
5. When PM2 publishes Master2, PWA's Project Details view on the workspace
will show all tasks from within the project INCLUDING the tasks from SubA.
My reason for this scenario:
I want the benefit of the cross-project dependencies, but I want the ability
for the dependency to be a full work package, not a single task. PM2 should
not have to worry about whether the work packages increases or decreases in
number of tasks. They simply want to see work package continue to change, and
see how it affects their full schedule. Cross-project dependencies would be
perfect for me if it were possible to use the SUMMARY TASK of an external
project as the dependency, and for that master project to dynamically reflect
any inserted/deleted tasks from the external project. I am assuming this is
not possible, so I came up with the scenario above.
Is my thinking accurate?
Master 1 (Saved often by PM1. NEVER published.)
SubA (Saved and published ONLY by PM1. Stays checked out.)
SubB ""
SubC ""
SubD ""
SubE ""
Master 2 (Saved and published by PM2.)
SubA (PM2 is not allowed to touch SubA's tasks. He is allowed to only
insert it as read-only in their master. PM1 does all of the updating of SubA)
Can you please validate my assumptions:
1. This scenario is allowed by Server 2007
2. Any time they open Master2, PM2 will see changes made to SubA by PM1.
(perhaps not by an alert window that appears when changes are made in
cross-project dependencies, but if they have a discerning eye they would see
new dates as well as new tasks in the sub.)
3. When PM2 saves or publishes Master2, they will get an alert that says,
"SubA is a sub in another project and may be published. This might cause
problems when publishing." Although this alert pops up, PM2 is safe because
he never made any changes to SubA, AND because PM1 never published Master1.
When PM2 publishes Master2, there is no risk of "double-publishing" SubA's
assignments, etc. But Master2 will be able to be published.
5. When PM2 publishes Master2, PWA's Project Details view on the workspace
will show all tasks from within the project INCLUDING the tasks from SubA.
My reason for this scenario:
I want the benefit of the cross-project dependencies, but I want the ability
for the dependency to be a full work package, not a single task. PM2 should
not have to worry about whether the work packages increases or decreases in
number of tasks. They simply want to see work package continue to change, and
see how it affects their full schedule. Cross-project dependencies would be
perfect for me if it were possible to use the SUMMARY TASK of an external
project as the dependency, and for that master project to dynamically reflect
any inserted/deleted tasks from the external project. I am assuming this is
not possible, so I came up with the scenario above.
Is my thinking accurate?