When Do You Need a DevOps Coach?

Published: Sept. 18, 2020, noon

We have a special repeat guest on this week\u2019s episode! It\u2019s Barry Matheney. He is a Senior DevOps Consultant and one of Dan\u2019s colleagues at AgileThought.

Get our Download Would you benefit from a DevOps Coach?\xa0

So often, teams operate on a \u201cget it done\u201d model and try to push their code out the door as quickly as possible, but that is not sustainable and not the markings of a high-class professional team. Barry understands the Scrum Teams\u2019 main mission and purpose is often very wrong; it\u2019s to appease the product owner, not create purposeful and meaningful end-results.

In this week\u2019s episode, Barry shares his thoughts on when it\u2019s time to hire a DevOps coach for an organization, some of the troubles organizations run into (problems with easy fixes!) when it comes to their Scrum Teams, and when you know when your team is on the right track in their DevOps journey.

Key Takeaways

What\u2019s the working definition of DevOps?

  • It\u2019s about delivering better value, sooner, safer, and happier.
  • The difference between Agile and DevOps\u2019s motto is the definition of what \u201cdone\u201d truly means.
  • True North for DevOps means there are a continuous delivery and a continuous deployment.
  • If you have some DevOps influence in what you\u2019re doing, you\u2019re on the right track.

What are the best ways a Scrum Team can get started?

  • Typically, when a Scrum Team gets started, the sole focus tends to be delivery of stories. AKA, making the product owner happy.
  • Most product owners don\u2019t care about dashboards or reliability. However, they should. The scope of a product owner should include the production world, as well.

When do you need a DevOps coach?

  • It\u2019s a tough answer. It depends on the team composition.
  • If you have a junior team, they won\u2019t have the experience to know the consequences of bad code.
  • The journey begins as soon as you begin production.
  • You build resiliency by delivering something that cannot fail, something that was built to last. That takes planning and continuous development. Junior teams might not be thinking in these terms just yet.

How do you know when you should be leveraging DevOps?

  • What times do your deployments occur? If you deploy them during off-hours, then something is wrong.
  • Deployments should be normal working events and not interruptions to your life.
  • Do your organization\u2019s security teams always seem to be diving into your business?
  • You can provide compliance and proof to your security teams you\u2019re on the right track and have thought about all the possible security risks.
  • Anything that happens should be logged.
  • You don\u2019t need to manually tinker in production.
  • Software teams want to get things out the door, but that\u2019s not operating at a professional level.
  • The transformation is not about your scrum team. It is an organizational transformation.

What\u2019s the distinction between an Agile coach vs. a DevOps coach?

  • Agile coaches plant the ideas.
  • DevOps coaches can help build the prototypes together and experiment with different theories.
  • DevOps coaches give a continuous approach and re-examine practices that were put into place 10 years ago that may not be relevant now.
  • DevOps is an organizational challenge, not necessarily a team challenge.
  • Waste is bad, so you need to either scrap the project or get it into production.\xa0
  • Remember, DevOps is a journey.

Mentioned in this Episode:

Would you benefit from a DevOps Coach?\xa0free download

AgileThought Event: \u201cVirtual Community: Building an Agile Mindset During COVID-19\u201d

Barry Matheney (LinkedIn)

Podcast Ep. 17: \u201cEmbedding DevOps in Large Organizations, with Barry Matheney\u201d

Podcast Ep. 12: \u201cThe Importance of Embedding a DevOps Skill Set into Your Team\u201d

Greenfield Project

Podcast Ep. 4: \u201cSetting Up Working Agreements with Christy Erbeck\u201d
Strangler Pattern

Podcast Ep. 2: \u201cWhat is a Full-Cycle Developer?\u201d

\xa0

Want to Learn More or Get in Touch?

Visit the website and catch up with all the episodes on AgileThought.com!

Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!