Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
75:instantiate [2020/06/11 21:23] – [Initialize Process Execution Systems] aakr | 75:instantiate [2024/02/09 19:17] – emr | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Instantiate a Process in a Workspace ====== | ====== Instantiate a Process in a Workspace ====== | ||
- | The process of instantiation is taking the standard process and giving | + | Process |
- | In Stages, | + | 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 | ||
+ | * Project-specific work products can be managed directly in the process | ||
===== Role of Process Architecture and Tailoring ===== | ===== Role of Process Architecture and Tailoring ===== | ||
Line 13: | Line 17: | ||
===== Create a new workspace ===== | ===== Create a new workspace ===== | ||
- | In order to instantiate a process for a new program or project, [[:72:manage_workspaces|new workspace]](s) must be created by the administrator. The location and level of the workspace is determing by the process architecture. New workspaces(s) for instantiated process allows control over process versioning, permission control, user addition as well as ability to push the instantiated processes into engineering tools like JIRA, RTC. Milestones and phases specific to project or program can also be modeled | + | In order to instantiate a process for a new program or project, [[:73:workspaces|new workspace(s)]] must be created by the administrator. The location and level of the workspace is determing by the process architecture. New workspaces(s) for instantiated process allows control over process versioning, permission control, user addition as well as ability to push the instantiated processes into engineering tools like JIRA, RTC. Milestones and phases specific to project or program can also be modeled |
[[https:// | [[https:// | ||
Line 19: | Line 23: | ||
[[https:// | [[https:// | ||
- | Existing standard process will then be integrated into this new workspace by using the '' | + | Existing standard process will then be integrated into this new workspace by using the '' |
[[https:// | [[https:// | ||
- | The recommended practice is to choose '' | + | The recommended practice is to choose '' |
[[https:// | [[https:// | ||
- | |||
===== Use Tailoring ===== | ===== Use Tailoring ===== | ||
Line 38: | Line 41: | ||
Next step would be add specific details like assigning users to roles and adding project specific work products. | Next step would be add specific details like assigning users to roles and adding project specific work products. | ||
- | + | ===== Assign | |
- | ===== Assign | + | |
A project manager can assign users for a given project or program. The user should already be present in Stages user list. This can be done by assigning the user to a role within the program or project. | A project manager can assign users for a given project or program. The user should already be present in Stages user list. This can be done by assigning the user to a role within the program or project. | ||
Line 47: | Line 49: | ||
[[https:// | [[https:// | ||
- | + | ===== | |
- | ===== Working with CM Systems | + | |
- | + | ||
- | Stages can interact with configuration management systems like Sharepoint, Subversion, Integrity to work with remotely stored files. Stages administator is responsible for this configuration. | + | |
===== ===== | ===== ===== | ||
- | |||
- | |||
- | ===== Assign users ===== | ||
- | |||
- | A project manager can assign users for a given project or program. The user should already be present in Stages user list. This can be done by assigning the user to a role within the program or project. | ||
- | |||
- | Navigate to the role e.g. Risk Manager and tap or click on Add. Next type the username or email in the search and select the user from the list. | ||
- | |||
- | [[https:// | ||
- | |||
===== Working with CM Systems ===== | ===== Working with CM Systems ===== | ||
Line 68: | Line 57: | ||
Stages can interact with configuration management systems like Sharepoint, Subversion, Integrity to work with remotely stored files. Stages administator is responsible for this configuration. | Stages can interact with configuration management systems like Sharepoint, Subversion, Integrity to work with remotely stored files. Stages administator is responsible for this configuration. | ||
+ | Refer to [[: | ||
- | ===== Initialize Process Execution Systems | + | ===== |