Going from a mediocre team to an elite team can seem daunting, especially when we need to figure out where to start. The DevOps Research and Assessment (DORA) can be our north star, helping us build the habits and practices we need to be elite. We'll look at DORA, the challenges of building habits, and how to form habits that stick. What Is DORA? The DevOps Research and Assessment (DORA) report focuses on four key areas to measure elite teams: Lead time: How long does it take from code committed to running in production
Deploy frequency: How often does our organization deploy to production
Change fail percentage: How often do we need to rollback, patch, hotfix, or fix forward after a change
Failed deployment recovery time: How long does it generally take to recover service The challenge here is going from knowing about those four areas that need to be worked on so that we go from being a mediocre team to an elite squad scoring a ten on the DORA quick check. The four measurements of an elite team are: Lead time is less than one hour


Deploy frequency is on-demand (multiple deploys per day)


The change fail percentage is ideally 0%


Failed deployment recovery time is less than one hour To see where tour team currently places, try the DORA quick check. This blog will focus on the tools, technologies, practices, culture, and philosophies that will help teams become elite. Improvements in our work take time since we need to break old habits that don't serve us well and build new ones. This blog will keep that in mind as we move through different topics. Each post will have an invitation to try out what we learn. If there are any questions or issues that need to be covered, make use of the comments section to submit the question. The Challenges of Forming New Habits We've all seen New Year's Resolutions and possibly have had some of our own. According to the Forbes report in 2024, 53% of those surveyed had given up on their New Year's Resolutions by the end of March. For many people, sticking to a new resolution or goal is challenging. There is now a day known as Ditch New Year's Resolution Day, which during 2024 fell on January 17th. While the media paints a picture of a significant stumbling block, statistics show it's less troublesome than perceived. We can see the reality of the quit rate in the chart below: Source Why Do People Fail in Their New Resolutions/Habits? In an article by James Clear, he outlines five reasons our new habits might fail: Trying to change more than one thing at a time


Setting big goals without breaking them down into smaller steps


Seeking a result, not the ritual


We have not changed the environment in which we perform our good habits, so we quickly revert to our bad habits


Assuming small changes don't add up However, there are ways to set ourselves up for success. In the book Atomic Habits, James talks about three key lessons: Small habits make a big difference.
Forget about setting goals. Instead, focus on the system.
Build identity-based habits. The Impact of Habits Building identity-based habits means, for example, instead of saying I go running, we say we're runners, or instead of saying we paint, we say we're painters. There is a subtle difference in the wording, but if we start to think we're runners, that can lead to thinking, what does a runner do? It could mean changing the food we eat, how often we train, when we train, and the goals we set for ourselves. If we focus on getting 1% better every day in one year, we'll end up being 37 times better than when we started. It means that anything we set our mind to can profoundly impact us. It may not be noticeable at first, but as the changes compound over time, we will notice that we're a different person than when we started. Like a cliff being eroded over time by the waves, at the start, we overlook the impact each wave has, but over time, we see how the cliff face changes in its shape. How Do I Go About Creating and Maintaining Habits? In the Habits Cheatsheet, James Clear talks about the four laws to create a good habit: The 1st law (Cue): Make it obvious
The 2nd law (Craving): Make it attractive
The 3rd law (Response): Make it easy
The 4th law (Reward): Make it satisfying As an example, let's say we've decided that we want to drink more water every day. We could make it obvious by placing a water bottle on our desk so that we can't miss it. Having a nice bottle or putting some lemon or mint in the water would be attractive. To make it easy, we fill the water bottle the night before so we don't have to think about it in the morning. Then, to make it satisfying, we could have a calendar above our desk where we put a sticker to mark each day that we've managed to empty our water bottle. How Do I Beat My Old Bad Habits? Again, in the Habits Cheatsheet, there are the inverse laws for avoiding our bad habits: Inversion of the 1st law (Cue): Make it invisible
Inversion of the 2nd law (Craving): Make it unattractive
Inversion of the 3rd law (Response): Make it difficult
Inversion of the 4th law (Reward): Make it unsatisfying Let's say we want to watch less TV. We could make it invisible by placing the TV out of view, moving it to another room, or inside a cupboard. We might unsubscribe to our streaming accounts and TV subscriptions to make it unattractive. To make it difficult, we place the TV's power cord or remote control in another room. Finally, to make it unsatisfying, we could have an accountability partner that we check in with, with whom we will have to confess that we ended up watching TV. The Next Steps As we reflect on our DORA scores, we have an opportunity to identify areas where we can improve by forming new habits. The DORA quick check provides guidance on key areas we can work on to improve our score. In our team, we can decide what to work on to raise our score, moving us from developers to software craftspeople. Then, we can form habits to help us make lasting changes. For example, if we identify a need to reduce lead time, we may realize our review process is slowing us down. When we explore it, we recognize we need to set aside time to review the code. We could take a habit-stacking approach. For example, when we open our laptops in the morning (our current habit), we first review all of the pull requests that are pending review for us. Another could be first to review pull requests after our lunch break. To make it attractive, we might realize that the pull requests lack enough information, so we add a pull request template so all the information is there. Then, to make it easy, we could have a simple way for people to launch the application and see the change. To make it satisfying, we could recognize a person each week who does a great job of meaningful reviews and helps speed up the delivery of features. Conclusion We've explored the DORA report and how it measures teams' ability to deliver software. We've examined how habits are the foundation of meeting our goals/resolutions, looking at good and bad habits. Our challenge is to move from software developers to software craftspeople, using our daily habits to help us transform. References State of DevOps Report: https://cloud.google.com/devops/state-of-devops
DORA quick check assessment: https://dora.dev/quickcheck/
Forbes article on New Year's Resolutions Statistics: https://www.forbes.com/health/mind/new-years-resolutions-statistics/
5 Common Mistakes That Cause New Habits to Fail: https://jamesclear.com/habits-fail
Atomic Habits book by James Clear: https://jamesclear.com/atomic-habits
Summary of the Atomic Habits book by James Clear: https://jamesclear.com/atomic-habits-summary
Continuous Improvement - How It Works and How to Master It: https://jamesclear.com/continuous-improvement
Habits cheatsheets: https://jamesclear.com/atomic-habits/cheatsheet
Habit stacking: https://jamesclear.com/habit-stacking The lead image was generated using Microsoft Designer. Going from a mediocre team to an elite team can seem daunting, especially when we need to figure out where to start. The DevOps Research and Assessment (DORA) can be our north star, helping us build the habits and practices we need to be elite. We'll look at DORA, the challenges of building habits, and how to form habits that stick. What Is DORA? The DevOps Research and Assessment (DORA) report focuses on four key areas to measure elite teams: report report Lead time: How long does it take from code committed to running in production Deploy frequency: How often does our organization deploy to production Change fail percentage: How often do we need to rollback, patch, hotfix, or fix forward after a change Failed deployment recovery time: How long does it generally take to recover service Lead time: How long does it take from code committed to running in production Lead time: Deploy frequency: How often does our organization deploy to production Deploy frequency: Change fail percentage: How often do we need to rollback, patch, hotfix, or fix forward after a change Change fail percentage: Failed deployment recovery time: How long does it generally take to recover service Failed deployment recovery time: The challenge here is going from knowing about those four areas that need to be worked on so that we go from being a mediocre team to an elite squad scoring a ten on the DORA quick check. The four measurements of an elite team are: The four measurements of an elite team are: Lead time is less than one hour Deploy frequency is on-demand (multiple deploys per day) The change fail percentage is ideally 0% Failed deployment recovery time is less than one hour Lead time is less than one hour Lead time is less than one hour Deploy frequency is on-demand (multiple deploys per day) Deploy frequency is on-demand (multiple deploys per day) The change fail percentage is ideally 0% The change fail percentage is ideally 0% Failed deployment recovery time is less than one hour Failed deployment recovery time is less than one hour To see where tour team currently places, try the DORA quick check . DORA quick check DORA quick check This blog will focus on the tools, technologies, practices, culture, and philosophies that will help teams become elite. Improvements in our work take time since we need to break old habits that don't serve us well and build new ones. This blog will keep that in mind as we move through different topics. Each post will have an invitation to try out what we learn. If there are any questions or issues that need to be covered, make use of the comments section to submit the question. The Challenges of Forming New Habits We've all seen New Year's Resolutions and possibly have had some of our own. According to the Forbes report in 2024, 53% of those surveyed had given up on their New Year's Resolutions by the end of March. For many people, sticking to a new resolution or goal is challenging. There is now a day known as Ditch New Year's Resolution Day, which during 2024 fell on January 17th. While the media paints a picture of a significant stumbling block, statistics show it's less troublesome than perceived. We can see the reality of the quit rate in the chart below: Source Source Why Do People Fail in Their New Resolutions/Habits? In an article by James Clear, he outlines five reasons our new habits might fail: article article Trying to change more than one thing at a time Setting big goals without breaking them down into smaller steps Seeking a result, not the ritual We have not changed the environment in which we perform our good habits, so we quickly revert to our bad habits Assuming small changes don't add up Trying to change more than one thing at a time Trying to change more than one thing at a time Setting big goals without breaking them down into smaller steps Setting big goals without breaking them down into smaller steps Seeking a result, not the ritual Seeking a result, not the ritual We have not changed the environment in which we perform our good habits, so we quickly revert to our bad habits We have not changed the environment in which we perform our good habits, so we quickly revert to our bad habits Assuming small changes don't add up Assuming small changes don't add up However, there are ways to set ourselves up for success. In the book Atomic Habits , James talks about three key lessons : Atomic Habits three key lessons three key lessons Small habits make a big difference. Forget about setting goals. Instead, focus on the system. Build identity-based habits. Small habits make a big difference. Forget about setting goals. Instead, focus on the system. Build identity-based habits. The Impact of Habits Building identity-based habits means, for example, instead of saying I go running, we say we're runners, or instead of saying we paint, we say we're painters. There is a subtle difference in the wording, but if we start to think we're runners, that can lead to thinking, what does a runner do? It could mean changing the food we eat, how often we train, when we train, and the goals we set for ourselves. If we focus on getting 1% better every day in one year, we'll end up being 37 times better than when we started. It means that anything we set our mind to can profoundly impact us. It may not be noticeable at first, but as the changes compound over time, we will notice that we're a different person than when we started. Like a cliff being eroded over time by the waves, at the start, we overlook the impact each wave has, but over time, we see how the cliff face changes in its shape. How Do I Go About Creating and Maintaining Habits? In the Habits Cheatsheet , James Clear talks about the four laws to create a good habit: Habits Cheatsheet The 1st law (Cue): Make it obvious The 2nd law (Craving): Make it attractive The 3rd law (Response): Make it easy The 4th law (Reward): Make it satisfying The 1st law ( Cue ): Make it obvious Cue The 2nd law ( Craving ): Make it attractive Craving The 3rd law ( Response ): Make it easy Response The 4th law ( Reward ): Make it satisfying Reward As an example, let's say we've decided that we want to drink more water every day. We could make it obvious by placing a water bottle on our desk so that we can't miss it. Having a nice bottle or putting some lemon or mint in the water would be attractive. To make it easy, we fill the water bottle the night before so we don't have to think about it in the morning. Then, to make it satisfying, we could have a calendar above our desk where we put a sticker to mark each day that we've managed to empty our water bottle. How Do I Beat My Old Bad Habits? Again, in the Habits Cheatsheet, there are the inverse laws for avoiding our bad habits: Inversion of the 1st law (Cue): Make it invisible Inversion of the 2nd law (Craving): Make it unattractive Inversion of the 3rd law (Response): Make it difficult Inversion of the 4th law (Reward): Make it unsatisfying Inversion of the 1st law ( Cue ): Make it invisible Cue Inversion of the 2nd law ( Craving ): Make it unattractive Craving Inversion of the 3rd law ( Response ): Make it difficult Response Inversion of the 4th law ( Reward ): Make it unsatisfying Reward Let's say we want to watch less TV. We could make it invisible by placing the TV out of view, moving it to another room, or inside a cupboard. We might unsubscribe to our streaming accounts and TV subscriptions to make it unattractive. To make it difficult, we place the TV's power cord or remote control in another room. Finally, to make it unsatisfying, we could have an accountability partner that we check in with, with whom we will have to confess that we ended up watching TV. The Next Steps As we reflect on our DORA scores, we have an opportunity to identify areas where we can improve by forming new habits. The DORA quick check provides guidance on key areas we can work on to improve our score. In our team, we can decide what to work on to raise our score, moving us from developers to software craftspeople. Then, we can form habits to help us make lasting changes. For example, if we identify a need to reduce lead time, we may realize our review process is slowing us down. When we explore it, we recognize we need to set aside time to review the code. We could take a habit-stacking approach. For example, when we open our laptops in the morning (our current habit), we first review all of the pull requests that are pending review for us. Another could be first to review pull requests after our lunch break. habit-stacking pull requests To make it attractive, we might realize that the pull requests lack enough information, so we add a pull request template so all the information is there. Then, to make it easy, we could have a simple way for people to launch the application and see the change. To make it satisfying, we could recognize a person each week who does a great job of meaningful reviews and helps speed up the delivery of features. Conclusion We've explored the DORA report and how it measures teams' ability to deliver software. We've examined how habits are the foundation of meeting our goals/resolutions, looking at good and bad habits. Our challenge is to move from software developers to software craftspeople, using our daily habits to help us transform. References State of DevOps Report: https://cloud.google.com/devops/state-of-devops DORA quick check assessment: https://dora.dev/quickcheck/ Forbes article on New Year's Resolutions Statistics: https://www.forbes.com/health/mind/new-years-resolutions-statistics/ 5 Common Mistakes That Cause New Habits to Fail: https://jamesclear.com/habits-fail Atomic Habits book by James Clear: https://jamesclear.com/atomic-habits Summary of the Atomic Habits book by James Clear: https://jamesclear.com/atomic-habits-summary Continuous Improvement - How It Works and How to Master It: https://jamesclear.com/continuous-improvement Habits cheatsheets: https://jamesclear.com/atomic-habits/cheatsheet Habit stacking: https://jamesclear.com/habit-stacking State of DevOps Report: https://cloud.google.com/devops/state-of-devops https://cloud.google.com/devops/state-of-devops https://cloud.google.com/devops/state-of-devops DORA quick check assessment: https://dora.dev/quickcheck/ https://dora.dev/quickcheck/ https://dora.dev/quickcheck/ Forbes article on New Year's Resolutions Statistics: https://www.forbes.com/health/mind/new-years-resolutions-statistics/ https://www.forbes.com/health/mind/new-years-resolutions-statistics/ https://www.forbes.com/health/mind/new-years-resolutions-statistics/ 5 Common Mistakes That Cause New Habits to Fail: https://jamesclear.com/habits-fail https://jamesclear.com/habits-fail https://jamesclear.com/habits-fail Atomic Habits book by James Clear: https://jamesclear.com/atomic-habits https://jamesclear.com/atomic-habits https://jamesclear.com/atomic-habits Summary of the Atomic Habits book by James Clear: https://jamesclear.com/atomic-habits-summary https://jamesclear.com/atomic-habits-summary https://jamesclear.com/atomic-habits-summary Continuous Improvement - How It Works and How to Master It: https://jamesclear.com/continuous-improvement https://jamesclear.com/continuous-improvement https://jamesclear.com/continuous-improvement Habits cheatsheets: https://jamesclear.com/atomic-habits/cheatsheet https://jamesclear.com/atomic-habits/cheatsheet https://jamesclear.com/atomic-habits/cheatsheet Habit stacking: https://jamesclear.com/habit-stacking https://jamesclear.com/habit-stacking https://jamesclear.com/habit-stacking The lead image was generated using Microsoft Designer. The lead image was generated using Microsoft Designer . Microsoft Designer Microsoft Designer

The is an opinion piece based on the author’s POV and does not necessarily reflect the views of HackerNoon.

Password Management and Protection - Part 1: The Basics

A Beginner's Guide to Pull Request Stacking

Portfolio

Read My Stories

Too Long; Didn't Read

Make resilience your competitive advantage

Elite Teams Are Built on Strong Habits

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

A Beginner's Guide to Pull Request Stacking

17 Ways to Motivate Your Dev Team

3 Must Have Practices for Distributed Developers

[Top 3] Time Management Habits of Highly Productive Distributed Teams

4 Tips to Improve Your Engineering Team's Velocity in Scrum

A Beginner's Guide to Pull Request Stacking

17 Ways to Motivate Your Dev Team

3 Must Have Practices for Distributed Developers

[Top 3] Time Management Habits of Highly Productive Distributed Teams

4 Tips to Improve Your Engineering Team's Velocity in Scrum

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps