Chapter 4. Controlling Changes and Releases

All changes or releases happen for one of two reasons:

  1. Proactively seeking business benefits, such as offering new features to customers, reducing costs, improving the service, implementing compliance/audit/security/organizational guidelines, and so on.
  2. Reactively resolving errors, bug fixes, and more.

A control process needs to be put in place to manage the risks associated with the changes and to effectively assess, optimize, and mitigate these risks, and all CIs must be put under this control process. A comprehensive Change Management System is required to support this process. In this chapter, we'll see how ServiceDesk Plus fits the bill and helps manage the change and release process flows. We'll cover ...

Get ServiceDesk Plus 8.x Essential now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.