Change and Release Management

This study investigates whether efficient Change and
Release Management processes can be implemented in a
high availability (i.e. Air Traffic Control)
environment and to gain insight how the processes
can be mapped onto the tool HP OpenView Service Desk
©. It shows that these processes can indeed be
implemented, giving opportunities for increasing
efficiency and effectiveness. A significant result
is the recognition that Change Management should
only be concerned with changes not requiring a
design phase else the request is to be forwarded
to the project management process. A further result
is that Change Management can easily be mapped onto
the tool while Release Management not explicitly
targeted by the tool is sufficiently supported by
using a feature to group changes. Finally it can be
concluded that the current tool version 5.1 supports
a database with customizable rules and actions and
personalized views but no workflows.or access to a
workflow engine.

Autorentext
Roland Schmidt started his career by joining the IT of the Austrian Air Navigation Services. He was involved in all aspcets of hardware and software, led QA and was responsible for the IT systems supporting Air Traffic Control. In 2001 he initiated the implementation of ITIL processes and supporting tools.

Klappentext
This study investigates whether efficient Change and Release Management processes can be implemented in a high availability (i.e. Air Traffic Control) environment and to gain insight how the processes can be mapped onto the tool HP OpenView Service Desk ©. It shows that these processes can indeed be implemented, giving opportunities for increasing efficiency and effectiveness. A significant result is the recognition that Change Management should only be concerned with changes not requiring a design phase - else the request is to be forwarded to the project management process. A further result is that Change Management can easily be mapped onto the tool while Release Management - not explicitly targeted by the tool - is sufficiently supported by using a feature to group changes. Finally it can be concluded that the current tool version 5.1 supports a database with customizable rules and actions and personalized views but no workflows.or access to a workflow engine.