E
Erik Klitzner
I just wanted to confirm what I believe. Templates that are created from
projects that have cross-project dependencies (i.e. predecessors and
successors in other projects) will retain the dependency info from the
projects from which they were created. New Projects that are created from
these templates will also retain the depenencies to/from the original
projects.
This is an issue for organizations that have large programs that they want
to bake into a set of templates. The process of creating templates would
require breaking all of these cross-project dependencies and then re-creating
them when a new set of projects are created from the templates.
Is there any guidance on how to make this process simpler or less error prone?
Thanks,
Erik
projects that have cross-project dependencies (i.e. predecessors and
successors in other projects) will retain the dependency info from the
projects from which they were created. New Projects that are created from
these templates will also retain the depenencies to/from the original
projects.
This is an issue for organizations that have large programs that they want
to bake into a set of templates. The process of creating templates would
require breaking all of these cross-project dependencies and then re-creating
them when a new set of projects are created from the templates.
Is there any guidance on how to make this process simpler or less error prone?
Thanks,
Erik