Differences

This shows you the differences between two versions of the page.

--- 75:instantiate [2024/02/06 18:59] – emr
+++ 75:instantiate [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 5: / Line 5: @@
 Some advantages of process instantiation are
+  * The version of a process instance can be kept stable. Even if the standard process from which it was initially derived from is being updated, the instance will not be impacted until a decision is being made to update it to a newer version.
   * Program, project, or other teams can rely on the defined process in their instance. Only the relevant processes are contained in this instance. Everything else is being tailored out.
-  * The version of a process instance will be stable. Even if the standard process from which it was initially derived from is being updated, the instance will not be impacted until a decision is being made to update it to a newer version.
+  * Project-specific work products can be managed directly in the process instance. Team members can directly access them, regardless of where they are actually stored (e.g. Sharepoint, SVN, Integrity). Project and program managers can see the status of work products across different storage repositories.
-  * Project-specific work products can be managed directly in the process instance. Team members can directly access them, regardless of where they are actually stored (e.g. Sharepoint, SVN, Integrity).
 ===== Role of Process Architecture and Tailoring =====