Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying The Cloud Adoption Playbook
  • Table Of Contents Toc
The Cloud Adoption Playbook

The Cloud Adoption Playbook

By : Moe Abdula, Ingo Averdunk, Roland Barcia, Kyle Brown, Ndu Emuchay
close
close
The Cloud Adoption Playbook

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)
close
close
Lock Free Chapter
1
Cover
2
Title Page
3
Foreword
16
Index
17
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...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
The Cloud Adoption Playbook
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon