Студопедия
Случайная страница | ТОМ-1 | ТОМ-2 | ТОМ-3
АвтомобилиАстрономияБиологияГеографияДом и садДругие языкиДругоеИнформатика
ИсторияКультураЛитератураЛогикаМатематикаМедицинаМеталлургияМеханика
ОбразованиеОхрана трудаПедагогикаПолитикаПравоПсихологияРелигияРиторика
СоциологияСпортСтроительствоТехнологияТуризмФизикаФилософияФинансы
ХимияЧерчениеЭкологияЭкономикаЭлектроника

The Service Transition manager

Читайте также:
  1. Advertising: Any paid form of nonpersonal presentation and promotion of ideas, goods, or services by an identified sponsor.
  2. Big Interpreter Service
  3. Can shares be issued in consideration for the contribution of assets or services (present or future)? Are any formalities required if shares are issued for non-cash consideration?
  4. Can shares be issued in consideration for the contribution of assets or services (present or future)? Are any formalities required if shares are issued for non-cash consideration?
  5. Consumption, take account of, manager, state, environment, include, capital, macroeconomics, economy
  6. Continuing education in the public service
  7. Customer service

The Service Transition manager has day-to-day management and control of the Service Transition teams and their activities. The prime responsibilities for this role are:

Planning and support

Planning and support may not be a direct responsibility of the Service Transition manager, as in some organizations this function may be consolidated into an overall Service Management office/IT planning responsibility. Regardless of where this function sits, the role must still be performed.

This function provides support for the Service Transition teams and people. The activities include:

Service Asset and Configuration Management and Change

Management roles

Service Design is responsible for designing the baseline s appropriate for the service and identifying the relevant asset s and CIs with input from the business change manager(s) and others who have responsibilities for delivering services and maintaining business continuity.

During the first stages of a project the programme or project office may be responsible for administering the Configuration Management process, maintaining copies of relevant documentation concerning the CIs, and controlling the release of CIs following appropriate approvals. At defined release points for a service and service package, the programme or project office will pass responsibility to Service Transition who will take responsibility for Configuration Management of the CI documentation.

Responsibilities for reviewing and approving assets and CIs across the service lifecycle and during deployment need to be defined and allocated to individuals with appropriate skills and authority.

Role specification s for the Change Management and Service Asset and Configuration Management teams need to be developed. Typical roles include:

Assign the configuration manager and other key roles as early as possible, because assigned individuals can then be involved in the implementation. For some operational activities Configuration Management will require staff who will adopt a diligent approach and pay due attention to detail.

The service asset manager

The service asset manager has the following responsibilities:

The configuration manager

The configuration manager has the following responsibilities:

The configuration analyst

The configuration analyst has the following responsibilities:

The configuration administrator/librarian

The configuration administrator/librarian is the custodian and guardian of all master copies of software, assets and documentation CIs registered with Asset and Configuration Management. The major tasks of this role are to:

The configuration administrator/librarian has the following specific responsibilities:

The CMS/tools administrator

The CMS/tools administrator has the following responsibilities:

The Configuration Control Board

The Configuration Control Board is required to ensure that the overarching intention and policies of Configuration Management are employed throughout the Service Management lifecycle and with specific consideration for every aspect of the complete service. The Board has the following responsibilities:

In some organizations, the Configuration Control Board will be combined with change, thereby providing a holistic view of the current and proposed services and service model s, enabling better control, change evaluation, impact assessment and understanding.

The change authority

Formal authorization is obtained for each change from a change authority that may be a role, person or a group of people. The levels of authorization for a particular type of change should be judged by the type, size or risk of the change, e.g. changes in a large enterprise that affect several distributed sites may need to be authorized by a higher-level change authority such as a Global Change Board or the Board of Directors.

The culture of the organization dictates, to a large extent, the manner in which changes are authorized. Hierarchical structures may well impose many levels of change authorization, while flatter structures may allow a more streamlined approach.

A degree of delegated authority may well exist within an authorization level, e.g. delegating authority to a change manager according to pre-set parameters relating to:

An example of authorization hierarchy is shown in Figure 4.5, Example of a change authorization model.

The change manager

The main duties of the change manager, some of which may be delegated, are listed below:

Change Advisory Board

A Change Advisory Board (CAB) is an advisory body. It needs to have appropriate terms of reference (e.g. meeting regularity, scope of influence, and links to programme management).

To understand more about the specific role and responsibilities of the CAB, see paragraph 4.2.6.8.

Performance and risk evaluation management

The following roles all provide input into the performance and risk evaluation of the Service Transition processes and key decision making, e.g. stopping or holding the deployment.

The performance and risk evaluation manager

The performance and risk evaluation manager has the following responsibilities:

Service Knowledge Management

Knowledge Management requires effective and authoritative ownership within an organization. The role of the Knowledge Management process owner is crucial, in that it will design, deliver and maintain the Knowledge Management strategy, process and procedure s.

The Knowledge Management process owner

The Knowledge Management process owner has the following responsibilities:

Service test manager

Service test management is primarily responsible for the test support and the test team(s) function s involved with the specific Service Transition. The service test manager will report to the Service Transition manager as will the release and deployment manager; however, these roles should always be undertaken by separate people, and never be combined, to ensure that there is always independent testing and test verification.

The service test manager has the following responsibilities:

Test support

The prime responsibility of the test support team is to provide independent testing of all components delivered within the Service Transition programme or project. Responsibilities required to deliver successful service testing include the following, however, not all of these are the direct responsibility of the test support team:

Release and deployment

Release and deployment is primarily responsible for managing all aspects of the end-to-end release process. The release and deployment manager will report to the Service Transition manager as will the service test manager; however these roles should always be undertaken by separate people, and never be combined, to ensure that there is always independent testing and test verification.

The release and deployment manager

The release and deployment manager is responsible for the planning, design, build, configuration and testing of all software and hardware to create the release package for the delivery of, or changes to, the designated service.

The release and deployment manager has the following responsibilities:

However, some of these responsibilities will be delegated to the relevant release team sub-process.

The main component s to be controlled are:

All deliverable s need to be managed effectively, from development or purchasing, through customization and configuration, through testing and implementation, to operation in the live environment.

Release packaging and build

Release packaging and build management is the flow of work (establish requirement s, design, build, test, deploy, operate and optimize) to deliver applications and infrastructure that meet the Service Design requirements.

The release packaging and build manager

The release packaging and build manager has the following responsibilities:

The release packaging and build manager cannot perform this role in isolation; other function s with which there will be significant interface are:

Deployment

Deployment staff have the following responsibilities:

Early life support

It is often believed that early life support starts when the service has actually been transitioned into operational use. This is not the case. Early life support should be considered as an integral role within the release and deployment phase.

Early life support staff have the following key responsibilities:

Build and test environment management

The build and test environment function is primarily to ensure that all the relevant people have the appropriate environments, test data, versioned software etc. available at the time that they need it and for the right purpose. As environment resource s are normally limited, this role performs a coordinating and sometimes arbitrary role to ensure that resource s are used to maximum effect.

Build and test environment staff have the following key responsibilities:


Service Transition relationship with other lifecycle stages

Service Transition is presented as a discrete lifecycle step, but this should not be taken to imply that it can stand alone. Service Transition exists to deliver the concepts documented within Service Design through to Service Operation s for day-to-day management, and so without design and operations it has no purpose.

Upstream relationships for Service Transition


Дата добавления: 2015-10-29; просмотров: 113 | Нарушение авторских прав


Читайте в этой же книге: Inputs from Service Design | Types of testing | Process activities, methods and techniques | Verify test plan and test design | Risk management | Establishing data and information management procedures | Communication planning | Methods of communication | The emotional cycle of change | Stakeholder map and analysis |
<== предыдущая страница | следующая страница ==>
Organization models to support Service Transition| Justifying Service Transition

mybiblioteka.su - 2015-2024 год. (0.023 сек.)