You're reading from Industrializing Financial Services with DevOps Proven 360° DevOps operating model practices for enabling a multi-speed bank

Product type Paperback

Published in Dec 2022

Publisher Packt

ISBN-13 9781804614341

Length 364 pages

Edition 1st Edition

Concepts

DevOps

Author (1):

Spyridon Maniotis

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1:Introduction, Value Proposition, and Foundation

2. Chapter 1: The Banking Context and DevOps Value Proposition FREE CHAPTER

3. Chapter 2: The DevOps Multi-Speed Context, Vision, Objectives, and Change Nature

4. Part 2: The 360° DevOps Operating Model, Governance, and Orchestration Mechanisms

5. Chapter 3: The DevOps 360° Operating Model Pillars and Governance Model

6. Chapter 4: Enterprise Architecture and the DevOps Center of Excellence

7. Chapter 5: Business Enterprise Agility and DevOps Ways of Working Reconciliation

8. Part 3: Capability Engineering, Enablement, and Launch

9. Chapter 6: DevOps Software Development Life Cycle 360° Evolution and Engineering

10. Chapter 7: The DevOps 360° Technological Ecosystem as a Service

11. Chapter 8: 360° Regulatory Compliance as Code

12. Part 4: Adopt, Scale, and Sustain

13. Chapter 9: The DevOps Portfolio Classification and Governance

14. Chapter 10: Tactical and Organic Enterprise Portfolio Planning and Adoption

15. Chapter 11: Benefit Measurement and Realization

16. Chapter 12: People Hiring, Incubation, and Mobility

17. Chapter 13: Site Reliability Engineering in the FSI

18. Chapter 14: 360° Recap, Staying Relevant, and Final Remarks

19. Index

Why subscribe?

20. Other Books You May Enjoy

The tactic of DevOps minimum viable adoption

Not all your teams by default will follow the same DevOps evolution journey and reach the same adoption level at the same time. They have different starting points, capabilities, ambitions, contexts, and the like. Nonetheless, you need to somehow get them to align on certain DevOps evolution commonalities, defining the key evolution milestones that they all need to meet. To define and group those commonalities, I like to use the term DevOps minimum viable adoption. With this term, in this book we define the common DevOps adoption milestones that all the teams need to reach, no matter their situation, context, conditions, circumstances, or starting point. The concept is twofold and links very well to the production readiness review (PRR) framework that we discussed in the previous chapter. In my relatively extensive experience with DevOps adoption across the financial services industry, DevOps minimum viable adoption is the most pragmatic...