Skip to main content
Redhat Developers  Logo
  • Products

    Featured

    • Red Hat Enterprise Linux
      Red Hat Enterprise Linux Icon
    • Red Hat OpenShift AI
      Red Hat OpenShift AI
    • Red Hat Enterprise Linux AI
      Linux icon inside of a brain
    • Image mode for Red Hat Enterprise Linux
      RHEL image mode
    • Red Hat OpenShift
      Openshift icon
    • Red Hat Ansible Automation Platform
      Ansible icon
    • Red Hat Developer Hub
      Developer Hub
    • View All Red Hat Products
    • Linux

      • Red Hat Enterprise Linux
      • Image mode for Red Hat Enterprise Linux
      • Red Hat Universal Base Images (UBI)
    • Java runtimes & frameworks

      • JBoss Enterprise Application Platform
      • Red Hat build of OpenJDK
    • Kubernetes

      • Red Hat OpenShift
      • Microsoft Azure Red Hat OpenShift
      • Red Hat OpenShift Virtualization
      • Red Hat OpenShift Lightspeed
    • Integration & App Connectivity

      • Red Hat Build of Apache Camel
      • Red Hat Service Interconnect
      • Red Hat Connectivity Link
    • AI/ML

      • Red Hat OpenShift AI
      • Red Hat Enterprise Linux AI
    • Automation

      • Red Hat Ansible Automation Platform
      • Red Hat Ansible Lightspeed
    • Developer tools

      • Red Hat Trusted Software Supply Chain
      • Podman Desktop
      • Red Hat OpenShift Dev Spaces
    • Developer Sandbox

      Developer Sandbox
      Try Red Hat products and technologies without setup or configuration fees for 30 days with this shared Openshift and Kubernetes cluster.
    • Try at no cost
  • Technologies

    Featured

    • AI/ML
      AI/ML Icon
    • Linux
      Linux Icon
    • Kubernetes
      Cloud icon
    • Automation
      Automation Icon showing arrows moving in a circle around a gear
    • View All Technologies
    • Programming Languages & Frameworks

      • Java
      • Python
      • JavaScript
    • System Design & Architecture

      • Red Hat architecture and design patterns
      • Microservices
      • Event-Driven Architecture
      • Databases
    • Developer Productivity

      • Developer productivity
      • Developer Tools
      • GitOps
    • Secure Development & Architectures

      • Security
      • Secure coding
    • Platform Engineering

      • DevOps
      • DevSecOps
      • Ansible automation for applications and services
    • Automated Data Processing

      • AI/ML
      • Data Science
      • Apache Kafka on Kubernetes
      • View All Technologies
    • Start exploring in the Developer Sandbox for free

      sandbox graphic
      Try Red Hat's products and technologies without setup or configuration.
    • Try at no cost
  • Learn

    Featured

    • Kubernetes & Cloud Native
      Openshift icon
    • Linux
      Rhel icon
    • Automation
      Ansible cloud icon
    • Java
      Java icon
    • AI/ML
      AI/ML Icon
    • View All Learning Resources

    E-Books

    • GitOps Cookbook
    • Podman in Action
    • Kubernetes Operators
    • The Path to GitOps
    • View All E-books

    Cheat Sheets

    • Linux Commands
    • Bash Commands
    • Git
    • systemd Commands
    • View All Cheat Sheets

    Documentation

    • API Catalog
    • Product Documentation
    • Legacy Documentation
    • Red Hat Learning

      Learning image
      Boost your technical skills to expert-level with the help of interactive lessons offered by various Red Hat Learning programs.
    • Explore Red Hat Learning
  • Developer Sandbox

    Developer Sandbox

    • Access Red Hat’s products and technologies without setup or configuration, and start developing quicker than ever before with our new, no-cost sandbox environments.
    • Explore Developer Sandbox

    Featured Developer Sandbox activities

    • Get started with your Developer Sandbox
    • OpenShift virtualization and application modernization using the Developer Sandbox
    • Explore all Developer Sandbox activities

    Ready to start developing apps?

    • Try at no cost
  • Blog
  • Events
  • Videos

Let's clarify that DevOps question mark

December 18, 2013
Jen Krieger
Related topics:
DevOps
Related products:
Developer Tools

Share:

    Hey all, I'm Jen Krieger and I am Team Inception's Product Owner and Scrum Master/Agile Coach. Hopefully, you have read Bill Montgomery's blog post last week about Red Hat IT's DevOps' journey. He referred to Underpants Gnomes strategy and how to get from point A to point C if there is a big question mark in the middle. You could say my job on the team is to clarify that question mark. I'm going to share my method... but first, let's break down what the first 6 weeks of team activities looked like from my perspective:

    • Formed team in late October and immediately swarmed around a presentation to explain what we are doing, backlog, strategy & roadmap needed, limited time to talk to stakeholders, hey… maybe we should read some information on CI/CD and DevOps.
    • Do all the most critically needed steps for agile best practices surrounding team formation. We selected Kanban as an initial focus for Agile practices.
    • Continued to talk to stakeholders… held meetings.
    • Presented "What is Inception" to Red Hat IT, included cookie monster and cookies as a defense mechanism to ward off attendees sleeping during presentation.
    • Continuing to read Jez Humble & David Farley’s Continuous Delivery book and flip to the end of the book (spoiler alert!) to find the maturity model and how to use it … "OMG, why didn't we read this in the reverse direction?" #readtheindexnexttimedummy
    • Presentation. Then beer. Then sleep. Then beer.
    • Continued to talk to with stakeholders… more meetings.
    • Team self-organized and got some work done.
    • I went on vacation (sorry team!), but not really because I still read email every day, thought about the team every day, and read from my ever growing mountain of suggested work reading.
    • Came back… worked on articulating a better roadmap to include two central themes: Environments & Deployment | Monitoring
    • Got a start on setting up our environment so our own team can get work done. #sprint0
    • Continued to talk to stakeholders… more meetings… see a pattern?
    • Continued to work on team dynamics, including normalizing team flow times, team definition of done, workflow & standard operating agreements.
    • Agile training with Bob Galen and we made a list of other Agile team goals we need to work on.

    And here the team is today… and what have we delivered? To be fair to the team, I'm not going to say nothing. I certainly don't believe that. Given the time we've had and how well we work together already, we are ahead of the game logistically. But here are some initial lessons learned:

    1. Distractions are really bad for Agile Teams. I have allowed the team to become distracted by outside influences… a lot of them. In trying to include everyone in the decision making process, talk about what was cool and new, attend meetings to learn what other teams were doing, talk to folks outside of IT on what they were doing, insert random topic here, I probably exposed them to more conversations/meetings then they could generally tolerate. The noise of the incoming "please help us make this better" was and continues to remain hard to ignore.

    2. Don't be afraid to fail. My A-type personality initially tried for the "perfect roadmap" and I learned pretty soon that wasn't going to work. We need to focus on and try to address what is most painful now before I could ask the department to talk about what was next. See Broken Windows Theory and The Pragmatic Programmer Quick Reference Guide.

    My new strategy is to just course-correct as often and as many times as needed in conjunction with incoming feedback from stakeholders. Since we are Kanban, we have a lot more flexibility over the incoming work and the timing of those decisions. As far as providing feedback to upper management on progress to our long-term goal, well… ask me again later...

    3. Continuously challenge your stakeholder community to tell you what they want. Our backlog is in a woeful state and needs some love and attention. It's hard to get internal stakeholder time and trust to hear about what is needed. Here are some examples of me doing it poorly:

    • I didn't include all of the right people in conversations. I didn't even know some of them were out there!
    • I focused too much on our development community in the first initial few weeks... and hey, surprise! we have an operations community that is equally needful.
    • I'm still trying to figure out how to incorporate our multi-geo teams into the conversation so they actually feel like they have a stake in the game.
    • Whoops! We have an Agile community of practice and an Office of the CIO that is interested in how and what we are doing

    Now that I've bored you to tears... Here is Team Inception's "easy button" method to help populate that question mark.

    1. Use Jez Humble & David Farley’s CI/CD maturity model. Any model will work, though. If that is what is holding you up; stop talking, start working.
    2. Complete a survey to find out where your teams are.
    3. Look at the definition of where you are and where you want to be… and state what needs to happen to change. If your stakeholder community generally feels they are at Level -1 and want to be at Level 0, list what high-level things you need to do in order to achieve that. Hint: the maturity model gives you the answer.
    4. Now that you have a high-level list, order them in priority based on stakeholder feedback. Don't take a whole lot of time here. If you are working in an Agile construct, you can always change the order if something doesn't stick or feel right.
    5. Starting with your #1 priority item, define what it means for your department. As an example: we went through these steps and selected "automated deployment to some environments" for an initial focus. Our current and ever changing definition below.
    6. Start working.

    General components of automated deployments:

    1. An artifact repository - assumes we will accept artifacts from different places and does imply binary artifacts
    2. Standardization of packages & package metadata
    3. Automated distribution of artifacts
    4. Logging of the orchestration
    5. Gatekeeper - determine if we need an approval at any point during the deployment
    6. Complete a release manifest
    7. Orchestration of release - ensure all the moving parts happen in the right order at the right time
    8. Anything else? Leave your responses in the comments!
    Last updated: February 7, 2024

    Recent Posts

    • Ollama or vLLM? How to choose the right LLM serving tool for your use case

    • How to build a Model-as-a-Service platform

    • How Quarkus works with OpenTelemetry on OpenShift

    • Our top 10 articles of 2025 (so far)

    • The benefits of auto-merging GitHub and GitLab repositories

    Red Hat Developers logo LinkedIn YouTube Twitter Facebook

    Products

    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform

    Build

    • Developer Sandbox
    • Developer Tools
    • Interactive Tutorials
    • API Catalog

    Quicklinks

    • Learning Resources
    • E-books
    • Cheat Sheets
    • Blog
    • Events
    • Newsletter

    Communicate

    • About us
    • Contact sales
    • Find a partner
    • Report a website issue
    • Site Status Dashboard
    • Report a security problem

    RED HAT DEVELOPER

    Build here. Go anywhere.

    We serve the builders. The problem solvers who create careers with code.

    Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.

    Sign me up

    Red Hat legal and privacy links

    • About Red Hat
    • Jobs
    • Events
    • Locations
    • Contact Red Hat
    • Red Hat Blog
    • Inclusion at Red Hat
    • Cool Stuff Store
    • Red Hat Summit
    © 2025 Red Hat

    Red Hat legal and privacy links

    • Privacy statement
    • Terms of use
    • All policies and guidelines
    • Digital accessibility

    Report a website issue