DevOps.com

  • Latest
    • Articles
    • Features
    • Most Read
    • News
    • News Releases
  • Topics
    • AI
    • Continuous Delivery
    • Continuous Testing
    • Cloud
    • Culture
    • DataOps
    • DevSecOps
    • Enterprise DevOps
    • Leadership Suite
    • DevOps Practice
    • ROELBOB
    • DevOps Toolbox
    • IT as Code
  • Videos/Podcasts
    • Techstrong.tv Podcast
    • Techstrong.tv - Twitch
    • DevOps Unbound
  • Webinars
    • Upcoming
    • Calendar View
    • On-Demand Webinars
  • Library
  • Events
    • Upcoming Events
    • Calendar View
    • On-Demand Events
  • Sponsored Content
  • Related Sites
    • Techstrong Group
    • Cloud Native Now
    • Security Boulevard
    • Techstrong Research
    • DevOps Chat
    • DevOps Dozen
    • DevOps TV
    • Techstrong TV
    • Techstrong.tv Podcast
    • Techstrong.tv - Twitch
  • Media Kit
  • About
  • Sponsor
  • AI
  • Cloud
  • CI/CD
  • Continuous Testing
  • DataOps
  • DevSecOps
  • DevOps Onramp
  • Platform Engineering
  • Sustainability
  • Low-Code/No-Code
  • IT as Code
  • More
    • Application Performance Management/Monitoring
    • Culture
    • Enterprise DevOps
    • ROELBOB
Hot Topics
  • Innersourcing Open Source Principles in the Enterprise
  • Survey Surfaces Major Observability Challenges
  • Generative AI: The 90% Rule
  • Oracle Previews Latest Java 21 Innovations
  • Buildkite Acquires Packagecloud to Streamline DevOps Workflows

Blogs Doin' DevOps A Critical First Step in Bringing Dev and Ops Together

A Critical First Step in Bringing Dev and Ops Together

By: Martin J. Logan on April 2, 2014 Leave a Comment

We all want to deliver excellent software to our customers. We now have a greater awareness than ever before of the interconnectedness of all the activities required to do so. The agile movement started this but it was not until the advent of DevOps that Ops was considered part of the full picture. In this article I will explain an effective first step that agile organizations can take to complete the picture and bring ops more completely into the product development process.

Recent Posts By Martin J. Logan
  • How to Manage Risk, Regulation and Compliance Differently —and Better
  • Enough with the DevOps already
  • DevOps Culture Hacks
More from Martin J. Logan
Related Posts
  • A Critical First Step in Bringing Dev and Ops Together
  • Webinar: From DevOps to Dev-Test-Ops – Automate Your End-To-End Software Pipeline
  • Webinar: From DevOps to Dev-Test-Ops – Automate Your End-To-End Software Pipeline
    Related Categories
  • Doin' DevOps
  • Features
    Related Topics
  • agile methodology
  • devops
  • devops culture
  • devops process
  • Martin J. Logan
  • product development
Show more
Show less

Delivering excellent software starts with product definition and flows from those initial stories and designs, into dev, verification and testing, into production and then back again in the form of customer feedback and bugs. In reality the feedback paths represent a transitive closure of all activities just mentioned as you can see in the diagram below. Agile recognized the importance of feedback loops in good product development. Agile also realized that for the right information to flow, walls had to be broken down. The motto “Done means tested” arose and indicated that product owners were not done with a story, could not consider it closed, until it had been tested and they had verified it. This represented the integration of PM, development and QA functions. A huge step, but one step too short. Operations was still not viewed as a key part of building excellent software and there was not much insight into the fact that the feedback loop did not stop at testing. DevOps has recognized this shortfall and taken it to its logical conclusion – “Done means in production.”

Operational Excellence Feedback Loop

AWS Builder Community Hub

Product development is a cycle, a cycle that operations is a critical part of. In describing how all parts of the cycle can be integrated lets start at the most natural beginning; product definition. Product definition activities produce stories, designs, functional acceptance criteria (A.C.) and prioritization. In this phase we don’t produce all we need for the finished product but just enough to get us going. With popular agile methodologies like Scrum this is ideally not done solely by a product owner but instead in conjunction with dev and test at story grooming meetings, design reviews and sprint planning. In these meetings dev, QA and product communicate and negotiate stories, comment on designs, and flesh out acceptance criteria. In this way the stories, designs and acceptance criteria are improved and everyone gains an understanding of what is being built; they also become invested in it. A story may look something like this (abbreviated):

Story: Blog administrator can change user roles SO THAT users can be managed effectively

A.C: Given blog administrator is logged in
And on a user profile
When he selects a permission scheme from a permissions drop-down menu
Then the users permissions are updated and stored in the DB

This is a great start but it is not enough. If we are to be excellent we must modernize this just a bit and add in some DevOps spice.

A first step towards bringing ops effectively into the cycle is to include someone responsible for actually operating the software in the story and acceptance criteria grooming sessions, design reviews, and sprint planning meetings. The critical aspect is that when the team negotiates the acceptance criteria associated with a story it will be ops responsibility to ensure we for each story or feature the team adds success and failure metrics, initial alarm values and any operational functionality such as a kill switch that will be needed in order to operate the functionality effectively. So a story will now contain things like the following in the A.C. (acceptance criteria).

Given operation X fails
Then the metric operation-x:failed will be sent through the metrics feed

We will also alter our definition of done to make sure that a story will not be closed until we meet the ops driven acceptance criteria. For example: we can see the metrics we have defined in our A.C. show up on an ops dashboard. There are so many benefits to this such as folks that are unlucky enough to be on on-call will have participated in this story grooming and will know exactly what these metrics mean when they encounter an issue with them for the first time in production. Furthermore, they will know what operational levers they can pull or request to be pulled.

This first step represents a connection from product definition to dev, to QA, to operations. This connection is perfectly natural and intuitive when you think about it. Being a true DevOps organization and developing operationally excellent products requires more but having connected product definition to operations as we have provides a nice toe hold from which to flesh things out further. Best of luck. If you have any questions leave them as comments and I will respond as best I can.

Filed Under: Doin' DevOps, Features Tagged With: agile methodology, devops, devops culture, devops process, Martin J. Logan, product development

« DevOps & UX: A Star-Crossed Love Story
An Introduction to DevOps »

Techstrong TV – Live

Click full-screen to enable volume control
Watch latest episodes and shows

Upcoming Webinars

What AI Doesn't Know About Kubernetes in Production
Thursday, September 21, 2023 - 12:00 pm EDT
The Benefits of Accelerating Your Application Modernization Journey With AWS
Thursday, September 21, 2023 - 1:00 pm EDT
Cloud Security Turbocharged: A Wild Ride of Innovation, Threats and Staying Ahead
Friday, September 22, 2023 - 11:00 am EDT

GET THE TOP STORIES OF THE WEEK

Sponsored Content

JFrog’s swampUP 2023: Ready for Next 

September 1, 2023 | Natan Solomon

DevOps World: Time to Bring the Community Together Again

August 8, 2023 | Saskia Sawyerr

PlatformCon 2023: This Year’s Hottest Platform Engineering Event

May 30, 2023 | Karolina Junčytė

The Google Cloud DevOps Awards: Apply Now!

January 10, 2023 | Brenna Washington

Codenotary Extends Dynamic SBOM Reach to Serverless Computing Platforms

December 9, 2022 | Mike Vizard

Latest from DevOps.com

Innersourcing Open Source Principles in the Enterprise
September 21, 2023 | Bill Doerrfeld
Survey Surfaces Major Observability Challenges
September 20, 2023 | Mike Vizard
Generative AI: The 90% Rule
September 20, 2023 | Don Macvittie
Oracle Previews Latest Java 21 Innovations
September 19, 2023 | Mike Vizard
Buildkite Acquires Packagecloud to Streamline DevOps Workflows
September 19, 2023 | Mike Vizard

TSTV Podcast

On-Demand Webinars

DevOps.com Webinar ReplaysDevOps.com Webinar Replays

Most Read on DevOps.com

CloudBees Unfurls Dual CI/CD Strategy at DevOps World Event
September 14, 2023 | Mike Vizard
CloudBees CEO: State of Software Development is a Disaster
September 14, 2023 | Mike Vizard
Google De-Recruits 100s of Recruiters ¦ ARM Valued at $45½B in IPO
September 14, 2023 | Richi Jennings
Why Enterprises Should Embrace Data-Driven Software Management
September 15, 2023 | Alex Circei
Summit Highlights Open Source Software Security Progress
September 14, 2023 | Mike Vizard
  • Home
  • About DevOps.com
  • Meet our Authors
  • Write for DevOps.com
  • Media Kit
  • Sponsor Info
  • Copyright
  • TOS
  • Privacy Policy

Powered by Techstrong Group, Inc.

© 2023 ·Techstrong Group, Inc.All rights reserved.