Creating and managing Change and Release Management roles

This recipe provides details on creating and managing the roles required for Change and Release Management using SCSM.

Getting ready

You must plan to meet the following prerequisites before you complete this task:

  • Planning: Agree the Change and Release Management categories and roles (for example, use a table to capture the planning information). Plan for groups and queues for security scope filtering:

    Process

    Process role

    SCSM Security role (template)

    AD group

    Categories (area)

    Change Management

    Change Initiators

    Change Initiator

    SCSM - CR Change Analysts

    Standard - infrastructure

    Change Management

    Change Owners

    Change Managers

    SCSM - CR Change Managers

    All Change Management categories

    Release Management

    Release Owners

    Release Managers

    SCSM - RR Release Managers Analysts

    All Release Management categories

  • Installation and Authorization: You need to have successfully installed the SCSM product, be a user in the SCSM Administrators role and have the SCSM console open.

How to do it...

Follow these steps to create Change and Release management class security roles:

  1. Create SCSM Groups for Configuration Items in the scope of Change Management. Use the steps in the Creating a configuration item group recipe in Chapter 4, Building the Configuration Management Database (CMDB).
  2. Create SCSM views by using Change and Release category.
  3. Follow the steps detailed in the Creating and managing Service Request roles recipe to create the Change and Release management roles based on Change Initiators, Change Managers and Release Managers. Use the groups and views you create for the Change and Release management process to limit the scope of authority.

How it works...

The How it works... section in the Creating and managing Service Request roles recipe is applicable to this recipe. You must plan specifically for the Change and Release management process.

There are two typical scenarios for Change and Release Management process roles in organizations:

  • Virtual roles of the Incident Management team
  • Dedicated Change and Release Management team

In the first scenario, plan to use the AD groups created for the Incident Management roles as the assigned users of the Change and Release Management role. The authors recommend the best practice of creating dedicated groups by processing and adding the same users as members.

In the second scenario, plan the Change and Release Management roles using the RACI (Responsible, Accountable, Consulted and Informed) model as a guide. Use the agreed role plan to implement the SCSM role model.

There's more...

Built-in security roles that you can use as templates are great for testing, as they have implied and inherited permissions over all objects by default.

Using the built-in roles

The built-in roles provide a means to delegate SCSM security roles to the specific process areas. Plan to use custom roles to avoid granting unnecessary access to SCSM. The built-in roles are assigned global scope access to all work and configuration items. You must limit the scope of access using groups and views to avoid unplanned access to SCSM process areas.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
18.224.39.32