Template: Process
#################

+---------------------------+-------------------------------------------------+
| Status                    | draft, |gitcommitted|                           |
+---------------------------+-------------------------------------------------+
| Review                    | annualy: yyyy-mm-dd                             |
+---------------------------+-------------------------------------------------+
| Processowner              |                                                 |
+---------------------------+-------------------------------------------------+
| Prozessuser               |                                                 |
+---------------------------+-------------------------------------------------+
| Previous Process          | :doc: --                                        |
+---------------------------+-------------------------------------------------+
| Next Process              | :doc: --                                        |
+---------------------------+-------------------------------------------------+
| Documents                 |                                                 |
+---------------------------+-------------------------------------------------+

Definition
==========

Define here what is to be achieved with this process.

In a second paragraph, define what is not to be achieved with this process or
what is covered by other processes.

Legal Basis
===========

If there is a legal basis for the process, it can be specified here.
As this section will apply to very few processes, it is optional.

Description
===========

The exact process description does not have to follow any standard here.
What is important is a description of the process that is as formal and
unambiguous as possible - but nevertheless not clunky - description of the
process.

Subsection
----------

* foo
* bar

General Conditions
==================

Process Owner
-------------

Define the process owner.

Quality Assurance
-----------------

Quality standards that the process owner follows and the metrics against which
he by which he or she wants to measure the performance of the process.

Period of Execution
-------------------

Specify when or with which trigger the process starts. Possibly which
previous process must have been carried out.

Process User
------------

Define who has to follow this process.

Requirement Profile of Process User
-----------------------------------

The process owner defines here which requirements he places on a process user
and how he can obtain them through e.g. training.

Ressources to follow this Process
---------------------------------

Define, which ressources may be needed by the process user, so that they can
follow this process.
Ressources may be time or access rights to special files.