The person responsible for managing a release, called a Release Manager in the default version of Serena Release Control, has primary ownership role in the planning activities and has secondary ownership throughout the lifecycle.
As the release follows the states of the lifecycle, ownership of activities changes based on the roles responsible for various states of the release. The default roles are set up according to a common release workflow, and the roles given ownership at progressive states are the roles that would typically have the expertise needed for those states’ activities.
Example
Typical roles within a simplified release package workflow are shown in the following figure.
Example roles are described in the following table.
|
Role |
Description |
|
Application Owner |
The role in Serena Release Control that is the business owner of an application. An application owner is responsible for approving an application release during the planning stage and receives notifications of application release status. |
|
The role in Serena Release Control that performs builds for a release. This role may also be the Installation Manager in some organizations. |
|
|
Change Manager |
The role in Serena Release Control that is responsible for the IT Operations for the systems where the pre-production and production release environments reside. A change manager approves deployment into pre-production and production environments. |
|
Development Manager |
The role in Serena Release Control that is responsible for and approves development activities for a release. A development manager would typically be consulted during the release management process and provide approval on the content of a release package. |
|
The role in Serena Release Control that ensures that the deployment, or installation, of a release is done correctly and completely. An installation manager is assigned manual deployment tasks in Serena Release Control and is responsible for deployment of request packages into environments. This role may also be the Build Manager in some organizations. |
|
|
QA Manager |
The role in Serena Release Control that is responsible for and approves testing activities for a release. |
|
The role in Serena Release Control that is responsible for the automating the release deployment and resolving any deployment failures. For example, a release engineer may create deployment tasks for release packages. This role may be the Installation Manager or Build Manager in some organizations. |
|
|
The role in Serena Release Control that is responsible for releases within a particular organization. A release manager manages and monitors releases, plans releases in collaboration with development managers, and responds to successes, failures, and other statuses. |
|
|
|
NOTE Roles in the default version of Serena Release Control are Release Manager and Release Engineer. Roles for your organization may be customized and may include different roles than those described here. |