Improving DevOps with the help of DORA

Stelios Moschos
4 min readMay 18, 2023


DORA stands for DevOps Research and Assesment

Recently, I had the opportunity to interview for a fascinating position focused on enhancing the engineering processes within an organization. I was particularly impressed to discover that the company embraces progressive concepts like DORA (DevOps Research and Assessment). My initial encounter with DORA occurred three years ago during my enrollment in a course titled “DevOps Culture and Mindset” at UC Davies University, which was expertly instructed by Courtney Kissler. This experience further solidified my passion for driving positive change and continuous improvement in the realm of DevOps practices.

I eagerly sought to apply these methodologies in my job. I recall composing an email to my team, as well as the senior management, articulating how our existing challenges with sluggishness could be overcome by embracing following some of these methodologies in our development processes. By automating tasks such as testing and deployment, closely monitoring services, and efficiently identifying and addressing issues and bugs inherent in our ongoing software development, we could significantly enhance our overall productivity and effectiveness.

Photo by Sigmund on Unsplash

What is DORA?

Looking at the current situation, I have been considering ways to further enhance that project, and it’s clear that the solutions offered by DORA are closely aligned.

DORA stands for “DevOps Research and Assessment.” It is a research organization and framework that focuses on measuring and evaluating the effectiveness of DevOps practices within organizations. DORA conducts extensive studies and surveys to identify key metrics and best practices associated with high-performing DevOps teams.

DORA’s research has resulted in the development of the four key metrics commonly known as the “DORA metrics” or “DORA four key metrics.” These metrics are:

  1. Deployment Frequency: This metric measures how frequently an organization can deploy changes to production. High-performing DevOps teams typically have multiple deployments per day.
  2. Lead Time for Changes: It refers to the time it takes for a code change to go from development to production. This metric focuses on the speed of delivering new features, bug fixes, and enhancements.
  3. Change Failure Rate: This metric measures the percentage of changes that result in failure or require rollback. A low change failure rate indicates a more stable and reliable software delivery process.
  4. Mean Time to Recovery (MTTR): It measures the average time taken to restore services after a failure or incident occurs. A lower MTTR indicates better incident response and recovery capabilities.
Photo by Austin Distel on Unsplash

How to improve DevOps practices with DORA?

To improve DevOps practices with the help of the DORA (DevOps Research and Assessment) framework, you can follow these steps:

  1. Measure Your Baseline: Use the DORA metrics to assess your current DevOps performance in areas such as deployment frequency, lead time, change failure rate, and mean time to recovery. This will provide a baseline for improvement.
  2. Set Clear Goals: Identify specific areas where you want to improve and set clear goals that align with your organization’s objectives. For example, you may aim to increase deployment frequency or reduce lead time.
  3. Foster a Culture of Continuous Improvement: Encourage a culture that values learning, collaboration, and continuous improvement. Provide opportunities for teams to share knowledge, experiment with new tools and techniques, and implement feedback loops.
  4. Automation and Infrastructure as Code: Embrace automation and Infrastructure as Code (IaC) practices to streamline and standardize your deployment processes. Automate repetitive tasks, build robust testing frameworks, and manage infrastructure in a version-controlled manner.
  5. Collaboration and Communication: Promote cross-functional collaboration and effective communication between development, operations, and other teams involved in the software delivery process. Encourage the use of collaborative tools and practices, such as ChatOps or collaborative incident response.
  6. Implement Continuous Integration and Continuous Delivery (CI/CD): Implement CI/CD pipelines to automate the build, test, and deployment processes. Enable teams to deliver code changes frequently, reliably, and with reduced risk.
  7. Monitor and Measure: Implement comprehensive monitoring and observability practices to gain visibility into system performance, application behavior, and user experience. Use real-time metrics and feedback to identify areas for improvement and proactively address issues.
  8. Empower Teams with Autonomy: Provide teams with the autonomy and authority to make decisions and implement improvements. Encourage experimentation, risk-taking, and learning from failures.
  9. Learn from Industry Best Practices: Stay informed about industry best practices, emerging technologies, and evolving trends in DevOps. Attend conferences, participate in communities of practice, and leverage resources provided by DORA and other reputable sources.
  10. Regularly Evaluate Progress: Continuously assess and evaluate your progress against the set goals. Use the DORA metrics to track improvements over time and identify areas that require further attention.

Remember, improving DevOps is an iterative process, and it requires a combination of technical, cultural, and process changes. The DORA framework can provide valuable guidance, but it’s important to adapt and tailor the practices to your organization’s specific needs and context.

About me

As a DevOps engineer and technical writer, I am committed to providing high-quality services to my clients. With my expertise and experience, I can help you streamline your development processes and improve your overall software development lifecycle. Additionally, my technical writing skills enable me to communicate complex ideas and concepts in a clear and concise manner. Whether you need help with DevOps implementation, technical writing, or both, I can provide you with customized solutions that meet your specific needs. If you’re interested in learning more about my services, please visit my website at

If you find my articles and blogposts helpful, I would greatly appreciate your support in spreading the word. Please feel free to like and share my content with your network. Your support will not only help me reach a wider audience, but it will also help others benefit from the insights and expertise I share. Thank you for your support!