You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 6
Next »
Processes organize activities to create a defined business value.
A process is a description of the activities to take to create the intended result. It is typically a quite abstract specification.
To provide information on by whom, when, and why a process is run, use the procedure doctype.
If you need to get into greater detail about what steps are actually conducted, use the work instruction.
Properties
The document type it-process provides the following properties:
Superordinate Process
Processes may be composed. This is a reference to the superordinate process.
The value is typically automatically provided by the parent document.
Participants
A list of roles that take part in the process.
Reference the roles in the process description.
Sections
Description
Provide a description of the process.
You may also justify the existence of the process and why it is important to document it.
Value Stream Map
A diagram giving an overview over the process, the steps involved, the times they take and the time between the steps. The map makes the change potentials visible.
Objective
Describe the objective for this process. This should contain the business value.
Trigger
Describe the trigger that starts this process.
Output
Describe the output resources for this process.
Artifacts may be output to processes.
Activities
List the activities that are part of this process.
Typically activities are associated as children to this document. Activities run by more than one process are stored on the IT Activity Doctype homepage.
Outcome
Describe the result of the process.
Impact
Describe the impact the result of the process has.
Services
List of services using this process.
This list of automatically updated.
Notes
These are internal notes that are usually not exported and only visible to team members with write access.
But this is not a safe place to store sensible information. It is just a convenience for the reader to not be bothered with notes stored here for the authors for later use. The security level is about suppressing the representation by a CSS style. Therefore consider this as a convenience for the reader, not as a security tool.
References
For a document the references section contains pointers to resources that prove the statements of the document.
Often these proofs are not easily distinguishable from further information. In this case you may want to skip the reference section in favour for the resource list.
Resources
The resources section provides references to further information to the topic of the document.
This may be information on the internet provided by the resource or information in the team's information systems. Anything the reader of the resource might want to know, may be listed here.
