Book Image

The Cloud Adoption Playbook

By : Moe Abdula, Ingo Averdunk, Roland Barcia, Kyle Brown, Ndu Emuchay
Book Image

The Cloud Adoption Playbook

By: Moe Abdula, Ingo Averdunk, Roland Barcia, Kyle Brown, Ndu Emuchay

Overview of this book

As cloud technologies continue to challenge the fundamental understanding of how businesses work, smart companies are moving quickly to adapt to a changing set of rules. Adopting the cloud requires a clear roadmap backed by use cases, grounded in practical real-world experience, to show the routes to successful adoption. The Cloud Adoption Playbook helps business and technology leaders in enterprise organizations sort through the options and make the best choices for accelerating cloud adoption and digital transformation. Written by a team of IBM technical executives with a wealth of real-world client experience, this book cuts through the hype, answers your questions, and helps you tailor your cloud adoption and digital transformation journey to the needs of your organization.
Table of Contents (17 chapters)
Free Chapter
Title Page
End User License Agreement

Root-Cause Analysis and Postmortems

A clear separation exists between incident management and problem management. Incident management focuses on restoring the service as quickly as possible through restarts, rollbacks, workarounds, and so on. Problem management aims to resolve the root causes of incidents to minimize their adverse effect and prevent recurrence. Both traditional ITSM and cloud-oriented service management agree on this separation, but they approach it in subtly different ways.

Root-cause analysis

Every defect is a treasure, if the company can uncover its cause and work to prevent it across the corporation.

— Kilchiro Toyoda, founder of Toyota

When the service is restored and the incident is closed, a series of follow-up activities to identify the incident’s root cause (or root causes) needs to take place. You can take proper countermeasures to make sure that the incident doesn’t reoccur only if you know the root cause.

The incident commander or site...