Bryan Finster

Information & Communications Technology

DevOps Value stream management Software Deveopment Software Engineering continuous delivery

Rogers, Arkansas, United States

Bryan Finster

Defense Unicorns - Value Stream Architect

Bryan Finster is a software engineer with over 25 years of experience delivering highly available systems for large enterprises. He founded and led the Walmart DevOps Dojo which focused on a hands-on, immersive learning approach to helping teams solve the problem of “why can’t we safely deliver today’s changes to production today?” He is the co-author of “Modern Cybersecurity: Tales from the Near-Distant Future”, the author of the “5 Minute DevOps” blog, a frequent industry speaker on all aspects of DevOps, and one of the maintainers of He is currently a value stream architect for Defense Unicorns working with the US Air Force's Platform One.

Deploy more and sleep better.

Current sessions

Scaling with Platform as a Product

Having a platform team focused on enabling product teams to deliver value sooner, safer, and happier can be a major force for elevating the outcomes of product development… if done correctly. In this talk, we’ll be discussing challenges and recommendations from lessons learned in implementing scalable delivery platforms in regulated environments. We’ll be covering key concepts of treating the platform as a product and ideas for keeping the platform team lean while scaling to growing demand.

Why Can't We CD?

As organizations move to continuous delivery, they will quickly discover that adding tooling will not get them there. We'll be discussing the common problems and how to overcome them that give teams the foundations to rapidly improve the flow of value.

Minimum Viable Continuous Delivery

"Accelerate" states, “Continuous delivery improves both delivery performance and quality, and also helps improve culture and reduce burnout and deployment pain.” Those of us who work this way know this is true. We also know that CD is a powerful tool for organizational improvement. Neither of these will be true if we aren’t using a real CD workflow. It is very common for teams and organizations to use incorrect definitions of CD. When they do, it harms outcomes, team morale, and is even causing CD to be banned in some organizations.

At the 2021 DevOps Enterprise Summit, several of us gathered at the Dockside Bar to discuss this problem we are witnessing. We formed a cross-industry group to try to help codify the minimum set of problems that need to be solved to see the benefits of continuous delivery in every context so everyone can live better lives. Three days later we published the first version of A week later we accepted a pull request from one of the fathers of CD, Dave Farley.

In this talk, we will cover the set of fundamental problems to be solved to achieve CD and how working to solve those problems acts as forcing functions for finding and removing the waste and pain that so many organizations are suffering daily. Everyone in the value stream should live better lives, and solving these problems will go a long way to getting us there.

How to Misuse and Abuse DORA Metrics

Since the 2018 release of Accelerate, DORA metrics have grown in popularity to measure development. However, there has also been a growth in using them for the wrong reasons resulting in poor outcomes. In this talk, I’ll be discussing common problems we are seeing with the spread of DORA metrics, how to use them appropriately, and try to dispel the myth that there are only 4.