CommunityDevOps ExchangePartners
Articles
9/13/2022
10 minutes

How the OODA Loop Decision-Making Model Drives DevOps Success

Written by
Team Copado
Table of contents

DevOps is an infinite cycle of improvement. You gather feedback through frequent testing, continuous monitoring, and user (or QA) bug reports. The goal is to take action based on that feedback to fix problems and improve a product with each iteration and release. The OODA loop decision-making model provides a systematic approach to applying feedback toward continuous improvement in a DevOps environment.

What is the OODA Loop Decision-Making Model?

The OODA loop is a military combat strategy adapted for many other stressful, fast-paced situations, including software development. The OODA loop decision-making model consists of four stages: Observe, Orient, Decide, and Act. The concept aims to break down the decision-making process into small, highly focused steps you can move through quickly and thoughtfully.

Observe. Collect and prioritize information about an incident, such as bug reports, monitoring data, or test results.

Orient. Analyze the observation data without biases to obtain an objective view of the problem and potential solutions.

Decide. Choose and flesh out a course of action that’s flexible, testable, and well-documented.

Act. Act upon the decision you’ve made and collect feedback on the results.

As the name suggests, the OODA loop is a recursive process that you’ll cycle through multiple times until the issue is resolved. You can also use the feedback from one OODA loop to improve the execution of a future OODA loop when a similar issue occurs.

How the OODA Loop Decision-Making Model Drives DevOps Success

DevOps is based on the Agile methodology, which encourages breaking down the software development pipeline into small, iterative steps. This process facilitates easy pivots when requirements change or issues arise, creating a more flexible (and agile) development process. 

The key to this kind of DevOps/Agile approach is shifting left, which means testing code as early and often as possible, often using automation for greater efficiency. This continuous testing increases the feedback frequency, determining what pivots are necessary to improve the next iteration.

The feedback collected from continuous testing typically kicks off the OODA loop decision-making model (see example below). However, as indicated above, feedback may come from monitoring alerts, user bug reports, and other sources.

Let’s look at an example of how one might use the OODA loop decision-making model within a DevOps pipeline.

Stage 1: Observation

A developer attempts to merge changes into the code base, but automated integration tests detect a defect. An incident is created and assigned back to the developer so they can review the test results. The developer may need to collect additional data, such as monitoring logs, but also must find a way to prioritize this information and weed out anything irrelevant.

Stage 2: Orientation

Rather than making a knee-jerk decision based on past experiences with similar problems, the developer attempts to discard their biases to view the issue with an open mind. They may conduct independent research or confer with their team. However, they should do so thoughtfully and without letting strong opinions sway their decision-making process.

Stage 3: Decision

The developer must now decide the best course of action. The ideal solution should be flexible so it can be altered as the situation evolves. It also needs to be testable, so the developer can immediately gather feedback on its efficacy (and potentially kick off another iteration of the OODA loop). Finally, it must be well-documented. That way, they know their actions, how those actions impacted the problem, and how to implement the solution.

Stage 4: Action

The developer puts their plan into action and observes the results. The observation may involve reviewing integration test results, monitoring and testing code as it moves through the pipeline, and collecting user feedback in production. By now, it should be obvious that this observation process is essentially the same as in stage one, meaning the developer is starting a new OODA loop. If all the feedback is positive, then stages 2-4 will progress fairly rapidly until the incident is closed.

DevOps and the OODA loop break down a larger process into small, iterative steps. In a DevOps environment, continuous testing and real-time monitoring ensure a constant flow of feedback, which means issues are caught as fast as possible. The OODA loop decision-making model uses continuous feedback to help teams quickly arrive at and implement an informed, methodical, and iterative action plan. The OODA loop drives DevOps success by providing a decision-making framework that facilitates development agility and constant improvement.

 

 

Book a demo

About The Author

#1 DevOps Platform for Salesforce

We build unstoppable teams by equipping DevOps professionals with the platform, tools and training they need to make release days obsolete. Work smarter, not longer.

Master Salesforce DevOps with Copado Robotic Testing
Exploratory Testing vs. Automated Testing: Finding the Right Balance
A Guide to Salesforce Source Control
A Guide to DevOps Branching Strategies
Family Time vs. Mobile App Release Days: Can Test Automation Help Us Have Both?
How to Resolve Salesforce Merge Conflicts: A Guide
Is Mobile Test Automation Unnecessarily Hard? A Guide to Simplify Mobile Test Automation
From Silos to Streamlined Development: Tarun’s Tale of DevOps Success
Simplified Scaling: 10 Ways to Grow Your Salesforce Development Practice
What is Salesforce Incident Management?
What Is Automated Salesforce Testing? Choosing the Right Automation Tool for Salesforce
Business Benefits of DevOps: A Guide
Copado Brings Generative AI to Its DevOps Platform to Improve Software Development for Enterprise SaaS
Celebrating 10 Years of Copado: A Decade of DevOps Evolution and Growth
Copado Celebrates 10 Years of DevOps for Enterprise SaaS Solutions
5 Reasons Why Copado = Less Divorces for Developers
What is DevOps? Build a Successful DevOps Ecosystem with Copado’s Best Practices
Scaling App Development While Meeting Security Standards
5 Data Deploy Features You Don’t Want to Miss
Top 5 Reasons I Choose Copado for Salesforce Development
How to Elevate Customer Experiences with Automated Testing
Getting Started With Value Stream Maps
Copado and nCino Partner to Provide Proven DevOps Tools for Financial Institutions
Unlocking Success with Copado: Mission-Critical Tools for Developers
How Automated Testing Enables DevOps Efficiency
How to Keep Salesforce Sandboxes in Sync
How to Switch from Manual to Automated Testing with Robotic Testing
Best Practices to Prevent Merge Conflicts with Copado 1 Platform
Software Bugs: The Three Causes of Programming Errors
How Does Copado Solve Release Readiness Roadblocks?
Why I Choose Copado Robotic Testing for my Test Automation
How to schedule a Function and Job Template in DevOps: A Step-by-Step Guide
Delivering Quality nCino Experiences with Automated Deployments and Testing
Best Practices Matter for Accelerated Salesforce Release Management
Maximize Your Code Quality, Security and performance with Copado Salesforce Code Analyzer
Upgrade Your Test Automation Game: The Benefits of Switching from Selenium to a More Advanced Platform
Three Takeaways From Copa Community Day
Cloud Native Applications: 5 Characteristics to Look for in the Right Tools
Using Salesforce nCino Architecture for Best Testing Results
How To Develop A Salesforce Testing Strategy For Your Enterprise
What Is Multi Cloud: Key Use Cases and Benefits for Enterprise Settings
5 Steps to Building a Salesforce Center of Excellence for Government Agencies
Salesforce UI testing: Benefits to Staying on Top of Updates
Benefits of UI Test Automation and Why You Should Care
Types of Salesforce Testing and When To Use Them
What is Salesforce API Testing and It Why Should Be Automated
Machine Learning Models: Adapting Data Patterns With Copado For AI Test Automation
Automated Testing Benefits: The Case For As Little Manual Testing As Possible
Beyond Selenium: Low Code Testing To Maximize Speed and Quality
UI Testing Best Practices: From Implementation to Automation
How Agile Test Automation Helps You Develop Better and Faster
Salesforce Test Cases: Knowing When to Test
DevOps Quality Assurance: Major Pitfalls and Challenges
11 Characteristics of Advanced Persistent Threats (APTs) That Set Them Apart
7 Key Compliance Regulations Relating to Data Storage
7 Ways Digital Transformation Consulting Revolutionizes Your Business
6 Top Cloud Security Trends
API Management Best Practices
Applying a Zero Trust Infrastructure in Kubernetes
Building a Data Pipeline Architecture Based on Best Practices Brings the Biggest Rewards
CI/CD Methodology vs. CI/CD Mentality: How to Meet Your Workflow Goals
DevOps to DevSecOps: How to Build Security into the Development Lifecycle
DevSecOps vs Agile: It’s Not Either/Or
How to Create a Digital Transformation Roadmap to Success
Infrastructure As Code: Overcome the Barriers to Effective Network Automation
Leveraging Compliance Automation Tools to Mitigate Risk
Moving Forward with These CI/CD Best Practices
Top 3 Data Compliance Challenges of Tomorrow and the Solutions You Need Today
Top 6 Cloud Security Management Policies and Procedures to Protect Your Business
What are the Benefits of Principle of Least Privilege (POLP) for My Organization?
You Can’t Measure What You Can’t See: Getting to know the 4 Metrics of Software Delivery Performance
How the Public Sector Can Continue to Accelerate Modernization
Building an Automated Test Framework to Streamline Deployments
How To Implement a Compliance Testing Methodology To Exceed Your Objectives
Cloud Security: Advantages and Disadvantages to Accessibility
Copado Collaborates with IBM to Accelerate Digital Transformation Projects on the Salesforce Platform
Continuous Quality: The missing link to DevOps maturity
Why Empowering Your Salesforce CoE is Essential for Maximizing ROI
Value Stream Management: The Future of DevOps at Scale is Here
Is Salesforce Development ‘One Size Fits All?’
The 3 Pillars of DevOps Value Stream Management
Gartner Recommends Companies Adopt Value Stream Delivery Platforms To Scale DevOps
The Admin's Quick Glossary for Understanding Salesforce DevOps
Top 10 Copado Features for #AwesomeAdmins