That Product Team Really Brought That Room Together

Many of the conflicts that we experience at work are the result of conflicting incentives, and this comes from how we are organized and incentivized. I will demonstrate what I consider to be the ideal DevOps implementation: the Product Team.

Much of the organizational problems come from an unexpected place: The Erie Railroad company in the 1850’s. Since this first org-chart, we have sliced our businesses along functional roles. And since those roles vary from slice-to-slice, each slice is evaluated based on different measurements. This is fine, right up until two slices have a relationship in which their measurements - their incentives - conflict.

In this talk, the audience will learn the source of this conflict, why the typical org-chart is causing more problems than it’s solving, how Product Teams help prevent code from becoming “Legacy”, and ensure that software is created sustainably.

The audience will learn what I consider to be the ideal model for working in a DevOps Culture, and the steps to take to get to the DevOps Promised Land.

Audience Takeaway: Why Product Teams are the best way to ensure that the right people are in the right “room”, how it ensures that incentives and business needs are aligned, and how that it ensures that software is written sustainably, and avoids creation of “Legacy” code.

Not much in the way of technical requirements. A confidence monitor would be great, and HDMI or Thunderbolt3/USB-C port will be enough for connectivity.