Chapter 93. Curating a DevOps Culture and Experience
Tiffany Jachja
DevOps came from the idea that by working together, developers and operations teams could drive the delivery of business value through software. I came to understand DevOps as a combination of people, process, and technology.
Admittedly, it took me quite some time to learn how these three areas played into each other. So I want to share three lessons about adopting DevOps practices and culture for developers, product owners, and stakeholders within organizations.
Define Your Target Outcomes
I’ve come to realize that things can go very wrong in any endeavors where the outcomes are not clearly defined and prioritized. Output and artifacts are significant; we produce them in design thinking sessions, feature building, and discovery sessions. However, these outputs and artifacts can quickly depreciate when teams misunderstand the goals and purpose.
The critical point here is not to confuse outcomes with outputs. You shouldn’t run a design sprint to produce a backlog for your developers to develop off of; this is an example of an output. An example of an outcome is having your critical stakeholders, including your developers, understand the problem space to begin developing the solution. If you’re running a session or event and have artifacts and checkboxes to produce, that’s great; it ensures ...
Get 97 Things Every Cloud Engineer Should Know now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
