Previous Topic

Book Contents

Book Index

Next Topic

Release Management Business Process

Open: The Release Management Business Process diagram

The Release Management Business Process diagram consists of the following main phases:

  • Planning
  • Build
  • Test
  • Approval

To successfully transfer a Release to the target environment, particular actions need to be performed. These actions are provided as tasks to the user until the approval is issued (the production release).

The corresponding process is based on the Valuemation Business Process Manager. The tasks are assigned to the participating groups from the planning phase till the release. They can be found in the 'Tasks – For me' catalog in the 'Processes' section in the Valuemation sidebar.

Tracking the release actions is also possible directly from the Release editor via a reference catalog of the related process task instances. Attributes of these tasks instances (date/time planned, date/time started, status, etc.) provide detailed information on each individual action.

The following actions in the Release process can be implemented or completed:

  • Request release

    A new Release is required.

  • Plan release

    The Release has been planned.

  • Build release

    The Release has been built.

  • Test release

    The Release has been tested.

  • Approve release

    The Release has been tested and must be approved before going into the production.

  • Release productive

    The Release has been deployed.

  • Release expired

    The Release has expired and is replaced with a newer version.

  • Release backout

    There is a problem with the productive Release and a rollback to the previous version is needed.

  • Release implementation failed

    The Release production phase failed.

  • Release cancelation

    The Release can be cancelled during any phase if needed.

The frequency of Releases can be defined as a dedicated service parameter for the related service.

Different phases for 'Planning', 'Build', 'Test' and 'Approval' are defined in the Release process. The corresponding mechanism for automation is available via the Business Process Manager.

The specific criteria for authorization (e.g. to finish the Early-Life Support and forward the Release to the normal operational phase) are also part of the process and can be influenced by the related service data.

See Also

Release Management

Release Management at a Glance

Important Object Types

Important Usecases

Release Lifecycle Statuses

Groups and Roles

Basic Categorization and Relations

Release Manager Object Types

Release Management Use Cases

Related Information

Create RFC out of Release