Cargando…
Industrializing Financial Services with DevOps Proven 360° DevOps Operating Model Practices for Enabling a Multi-Speed Bank /
Embrace best practices to advance and help evolve your DevOps operating model in the right direction and overcome common challenges that financial services organizations face. Purchase of the print or kindle book includes a free eBook in the PDF format. Key Features Design the right DevOps operating...
| Clasificación: | Libro Electrónico |
|---|---|
| Autor principal: | |
| Formato: | Electrónico eBook |
| Idioma: | Inglés |
| Publicado: |
Birmingham :
Packt Publishing, Limited,
2022.
|
| Edición: | 1st edition. |
| Temas: | |
| Acceso en línea: | Texto completo (Requiere registro previo con correo institucional) |
Tabla de Contenidos:
- Cover
- Title Page
- Copyright and Credits
- Contributors
- Table of Contents
- Preface
- Part 1: Introduction, Value Proposition, and Foundation
- Chapter 1: The Banking Context and DevOps Value Proposition
- Introducing the main actor of the book
- Examining the incumbent's external and internal context at a glance
- What does an incumbent bank's external context look like?
- Which are the forces that shape the financial services industry?
- What does an incumbent's internal context look like?
- Defining DevOps and its value proposition for banking
- What is the importance of adopting DevOps at relevance?
- Defining relevance
- The relevance of the situation level
- The relevance of sub-situation levels
- Why have a 360° perspective when adopting DevOps?
- Summary
- Chapter 2: The DevOps Multi-Speed Context, Vision, Objectives, and Change Nature
- Understanding multi-speed banking
- Why multiple speed levels arise out of different situations and ambitions
- What is the role of circumstances in enabling multi-speed?
- The role of individuals in multi-speed
- Understanding multi-speed banking in a DevOps adoption context
- Understanding your state-of-art DevOps context
- Why examining your state-of-art DevOps context is vital
- Once upon a time in Berlin
- Why industry imitation is decisive in shaping DevOps adoptions
- Are there several DevOps "states of the art" within an incumbent's context?
- What does a representative state of art DevOps adoption look like for an incumbent bank?
- Enterprise DevOps vision and objectives
- Recapping the forces and qualities that shape the DevOps vision
- Examining the incumbent's corporate and technology strategies
- Shaping the DevOps vision
- Defining the DevOps enterprise OKRs
- Deciding on the nature and extent of your DevOps adoption
- Why is it important to define and weigh the forces of your evolution?
- Summary
- Part 2: The 360° DevOps Operating Model, Governance, and Orchestration Mechanisms
- Chapter 3: The DevOps 360° Operating Model Pillars and Governance Model
- Defining the DevOps 360° operating model core pillars
- The evolution's core governance
- Establishing a DevOps 360° vision authority group
- Establishing a DevOps 360° design and advocacy group
- Defining your DevOps enterprise evolution ecosystem
- Who should be considered as key stakeholders?
- Defining the evolution's workstreams
- Bringing it together
- Understanding the governing dynamics
- Understanding the balance of power in the governing bodies
- Bringing two different worlds together
- Speaking the same DevOps language
- Understanding your organizational structure dynamics
- What to look for in your organizational structure
- Use case 1
- segregated business technology lines and group technology
- Use case 2
- segregated business and technology
- Use case 3
- consolidated business and technology domains segregated from the core technology