Juni Mukherjee

The Power of Continuous Delivery in Devops Juni Mukherjee

This book has TWO purchase options:

1) Color eBook.

2) Bundle of color paperback and color eBook.

View, print, and download all diagrams from http: //continuity.world/2017-book. Connect if you have questions at http: //continuity.world/connect.

Processes, amongst other things, can exponentially improve organizational culture. This book lays the foundation of building resilient processes for transformational leaders who aspire to drive culture change in their organizations. The principles of DevSecOps, Continuous Integration and Continuous Delivery form the recipe for success, and Continuous Improvement is at the heart of it.

As you plow through the chapters of this book, you will virtually experience the thrills and the shivers of leading a crucial transformational change. And you will be able to define the next chapter of your very own journey.

This is how I have structured the book:

Chapter 1: Introduction

Eases my readers into understanding and appreciating a Continuous Delivery Pipeline, extends the concepts to Continuous Everything and Everyone, and gives a brief introduction about myself.

Chapter 2: Continuous Delivery As A Domain

Domain-driven design (DDD) is known to be overkill for simple problems. After careful consideration of the issues that plague product releases (software, firmware, embedded systems, Internet of Things, * as a service, and the like), I decided to model the Continuous Delivery Pipeline as a domain.

Chapter 3: Pipeline Domain Model Integrity

In an academic setting of model-driven-development, we try to maintain a consistent and unified model throughout the teams. In reality, there could be many teams who work on different parts of the Continuous Delivery Pipeline ecosystem and the model tends to fragment. However, aspects of the model that are important should stay unified and other parts could be offered for customization.

Chapter 4: Continuous Analytics And Insights

Teams are required to zoom in and solve hard problems every day. While it is paramount to be able to get down on our knees and dig in, it is just as important to be able to zoom out and fathom the big picture. We need to see the forest through the trees. We should emphasize on learning patterns and trends over a period of time that offer direct insights into our business. These help us make tough calls that pay rich dividends in the long run.

Chapter 5: A DevSecOps Seed Backlog

A single prioritized Product Backlog is a key driver of an organization's growth and sustainability. This chapter enables Product Owners to address epics related to not just Development but also Builds, Tests, Configuration, Deployment, Monitoring, KPIs, Operations, Network, Security and related issues that help teams experiment safely and turn great ideas into products. More importantly, this helps teams recover fast from not-so-great ideas.

Chapter 6: The Twelve-Factor Pipeline

Inspired by The Twelve-Factor App, the Twelve-Factor Pipeline establishes the same gold standards for the Pipeline application, as are applied to the products that flow through the Pipeline.

Chapter 7: Segregation/Separation Of Duties

Segregation of duties or separation of powers is a controversial topic in organizations that have dwelled on a legacy hierarchy long enough to confuse separation of duties with separation of departments. This chapter establishes guidelines on how we should implement Continuous Delivery Pipelines that improve speed, quality, and predictability without risking business.

Chapter 8: Myth Busters

Some organizations fall prey to age-old beliefs that have inherent flaws. This results in modernized approaches getting the boot and new gen tech leads stumbling over bureaucracy and red tape. This chapter pulls up the most damaging myths and addresses the elephant(s) in the room.

Chapter 9: Resources

Lists a set of resources.