nach oben

2018 | Buch

Kapitel lesen Erstes Kapitel lesen

Reinventing ITIL® in the Age of DevOps

Innovative Techniques to Make Processes Agile and Relevant

verfasst von: Abhinav Krishna Kaiser

Verlag: Apress

Enthalten in: Springer Professional "Wirtschaft+Technik" , Springer Professional "Technik" , Springer Professional "Wirtschaft"

Einloggen, um Zugang zu erhalten

Über dieses Buch

Delve into the principles of ITIL® and DevOps and examine the similarities and differences. This book re-engineers the ITIL framework to work in DevOps projects without changing its meaning and its original objectives, making it fit for purpose for use in DevOps projects. Reinventing ITIL® in the Age of DevOpsshows you the relevance of ITIL since the emergence of DevOps and puts a unique spin on the ITIL service management framework. Along the way you will see that ITIL is a mature service management framework and years of maturity will be lost if it’s made invalid.
The ideas, recommendations, and solutions provided in Reinventing ITIL in the Age of DevOps can be leveraged in order to readily develop solutions or create proposals for clients. The ideas in this book can be further expanded to deliver seamless services to DevOps projects.
What You Will LearnDiscover the basics of ITIL and DevOps
Compare ITIL and DevOps
Understand the structure of a DevOps organization and adapt the ITIL roles to this structure
Re-engineer ITIL for DevOps projects
Implement major processes such as incident management, configuration management, and change management processes in DevOps projects
Automate activities within processes

Who This Book Is For
Consultants, business analysts, administrators, and project managers who are looking for more information about Dynamics 365.

Inhaltsverzeichnis

Frontmatter

Chapter 1. Introduction to DevOps

Abstract

New ways of working or new methodologies begin to unearth because of a problem---yes, it all starts with a problem. DevOps too had its own reasons. Businesses craved for fast turnarounds of their solutions. And often businesses found out in the midst of development that they didn’t have all the information they needed to make the right decisions. They wanted to recommend a few more changes to the requirements and still expected the delivery to happen on time. DevOps was born to solve this problem.

Abhinav Krishna Kaiser

Chapter 2. ITIL Basics

Abstract

The Information Technology Infrastructure Library (ITIL) is the most popular framework that exists today to deliver services. It has become a standard of sorts, and most service-based organizations have implemented one form of ITIL or another.

Abhinav Krishna Kaiser

Chapter 3. ITIL and DevOps: An Analysis

Abstract

In Chapters 1 and 2, DevOps and ITIL were introduced as an independent framework/methodology, and I consciously did not make an effort to bring together the two entities. I will analyze them together in this chapter. I will dissect the big-ticket conflicts, and the chapter will set the tone for the rest of the book to follow, in other words, for creating a union between the two rather than replacing one with the other. Chapters 1 and 2 clearly specify that the two are leaders in their own respective areas, and one cannot reasonably replace the other. The question of replacement has arisen because the newer of the two, DevOps, steps on ITIL’s foot and claims to take over certain aspects of service management.

Abhinav Krishna Kaiser

Chapter 4. Integration: Alignment of Processes

Abstract

From this chapter on, we start with the exercise of aligning the ITIL service management framework for a DevOps project. The exciting bit starts here! The exercise involves looking at ITIL holistically and identifying the phases and processes that can stay as is and those that need to rejigged.

Abhinav Krishna Kaiser

Chapter 5. Teams and Structures

Abstract

Processes provide the guidance around the objectives to be met and the outcomes to deliver. They provide all the directions necessary for an organization to succeed. But, processes are not executed by machines (mostly). People are required to carry out the tasks set forth. People are extremely unpredictable, and our analog nature does not guarantee outcomes no matter how well the processes have been laid out. Therefore, it is imperative that the teams be set up for maximum chances of success. The setup for success starts with the team structure as the team’s motivation, orientation, and enthusiasm stem from the home base. The teams and their structure are the focus of this chapter, which is aimed at delivering faster and with abnormal accuracy.

Abhinav Krishna Kaiser

Chapter 6. Managing Configurations in a DevOps Project

Abstract

Most projects fail because of the lack of managing configurations and having total control over the various components that make a project tick. Configuration management is the foundation upon which the entire project is built. Giving no care to the foundation will logically see the walls and roofs of the project crumbling down in record time. Configuration management plays a significant role for systems made up of multiple components that are integrated with other systems and run on multiple dependencies. Sound familiar? Yes, most systems today are complex owing to the need for integration and its respective data sources and data consumers. In such a complicated setup, it is imperative that systems are driven by configuration management, which is relied on heavily by projects, which, in our context, are DevOps projects.

Abhinav Krishna Kaiser

Chapter 7. Incident Management Adaption

Abstract

Whenever somebody refers to IT service management or ITIL, the first process that comes up on the table for discussion is the incident management process. No matter how far away one might be from the service management area, they always seem to be quite familiar with the process and its relevance. It is a highly popular process that finds its rightful place in every single organization. Since this process makes or breaks an organization’s service delivery, service providers often give plenty of weight to the process, and as a result, the incident management process is perhaps the most mature of all the ITIL processes.

Abhinav Krishna Kaiser

Chapter 8. Problem Management Adaption

Abstract

Incident management is the first line of defense in providing immediate relief against the disruption of services and eventual downtimes. However, by no means does the incident management process get into the nitty-gritty of putting an end to the cause behind the incidents. Its purpose is to bring the services back up, even if the solution is a nonpermanent one.

Abhinav Krishna Kaiser

Chapter 9. Managing Changes in a DevOps Project

Abstract

They say that change is the only constant. They also say that anything that does not grow withers away. This is so true in the software industry. No matter how old the software or the service is, changes to it happen all the time. No matter how legacy the application is, it still needs to be maintained and made current to the organizational needs.

Abhinav Krishna Kaiser

Chapter 10. Release Management in DevOps

Abstract

We have come to the end of the adaptation transformation of ITIL processes into DevOps projects. Release management is the final (major) process that needs to be adapted to the swift and Agile way of developing and promoting deployments into various environments.

Abhinav Krishna Kaiser

Backmatter

Titel: Reinventing ITIL® in the Age of DevOps
verfasst von: Abhinav Krishna Kaiser
Verlag: Apress
Electronic ISBN: 978-1-4842-3976-6
Print ISBN: 978-1-4842-3975-9
DOI: https://doi.org/10.1007/978-1-4842-3976-6