Podcasts about devops it

We have a special repeat guest on this week’s episode! It’s Barry Matheney. He is a Senior DevOps Consultant and one of Dan’s colleagues at AgileThought. Get our Download Would you benefit from a DevOps Coach?  So often, teams operate on a “get it done” 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’ main mission and purpose is often very wrong; it’s to appease the product owner, not create purposeful and meaningful end-results. In this week’s episode, Barry shares his thoughts on when it’s 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’s the working definition of DevOps? It’s about delivering better value, sooner, safer, and happier. The difference between Agile and DevOps’s motto is the definition of what “done” 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’re doing, you’re 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’t 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’s a tough answer. It depends on the team composition. If you have a junior team, they won’t 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’s security teams always seem to be diving into your business? You can provide compliance and proof to your security teams you’re on the right track and have thought about all the possible security risks. Anything that happens should be logged. You don’t need to manually tinker in production. Software teams want to get things out the door, but that’s not operating at a professional level. The transformation is not about your scrum team. It is an organizational transformation. What’s 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.  Remember, DevOps is a journey. Mentioned in this Episode: Would you benefit from a DevOps Coach? free download AgileThought Event: “Virtual Community: Building an Agile Mindset During COVID-19” Barry Matheney (LinkedIn) Podcast Ep. 17: “Embedding DevOps in Large Organizations, with Barry Matheney” Podcast Ep. 12: “The Importance of Embedding a DevOps Skill Set into Your Team” Greenfield Project Podcast Ep. 4: “Setting Up Working Agreements with Christy Erbeck”Strangler Pattern Podcast Ep. 2: “What is a Full-Cycle Developer?”   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!

Quality is an integral part of Digital Transformation. The number one goal of Digital Transformation in any DevOps/ IT organization is to improve the end-user experience. In this episode, Chris Rowett, Vice President of Customer Success at SeaLights, will share his insight on what he has seen work for teams involved in such transformations. He’ll explain how to make smarter release decisions, tactics and execution advice, and real-world examples. Listen up!

Your host, Dan Neumann, is excited to bring you two guests for this week’s episode — repeat guest, Eric Landes, and Barry Matheney. Eric and Barry are both Agile thinkers, experts in the DevOps space, and colleagues of Dan at AgileThought.   Eric Landes is a Scrum.org certified professional Scrum trainer and currently serves as a Senior DevOps Consultant, ALM Director, and Solutions Architect. Barry also is a Senior DevOps Consultant. Previously to his role at AgileThought, he served as Director Enterprise Applications at Kforce Inc.   Today, they’re talking about DevOps and the importance of having it on Scrum teams. They cover whether it is good or bad that there are barriers between Agile, Scrum, and DevOps; what well-functioning Scrum teams look like when they have a DevOps skillset embedded into them; how to incorporate DevOps into organizations; what a DevOps skillset could bring to a team; and how DevOps can fit into even the most traditional of companies.   Key Takeaways Is it good or bad that there are barriers between Agile or Scrum and DevOps? It is disadvantageous to separate DevOps from Agile or Scrum because it is important that your team has all the skills they need to deliver software You need the DevOps skillset on your team and it should be a goal to incorporate it What do well-functioning Scrum teams look like when they have DevOps skillsets embedded into them? Self-sufficient Not limited by dependence on other teams or organizations Eliminates walls and allows for continuous delivery How to incorporate DevOps into organizations: Use baby steps Use it to inform the beginning of the development cycle and product decisions down the line What the DevOps skillset brings to a team: Experimentation or hypothesis-driven development Rapid deployment and continuous delivery Tons of not-so-visible benefits (such as auditing, compliance, security, deployability, and testability) How DevOps can fit into traditional companies: Remove constraints (such as specific deployment dates) Automate the value the compliance brings   Mentioned in this Episode: Eric Landes (LinkedIn) Barry Matheney (LinkedIn) The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations, by Gene Kim, Patrick Debois, John Willis, and Jez Humble Podcast Ep. 9: “Exploring Expert Facilitation Tips with Adam Ulery” SRE — Site Reliability Engineering Cowboy coding   Eric Landes and Barry Matheney’s Book Picks The Age of Agile: How Smart Companies Are Transforming the Way Work Gets Done, by Stephen Denning Lean Enterprise: How High Performance Organizations Innovate at Scale, by Jez Humble, Joanne Molesky, and Barry O’Reilly Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations, by Nicole Forsgren PhD, Jez Humble, and Gene Kim Outliers: The Story of Success, by Malcolm Gladwell   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!

Today on the Agile Coaches’ Corner, your host, Dan Neumann invites on Sean Davis to explore the DevOps movement. Sean is one of Dan’s colleagues at AgileThought and is a DevOps expert and frequent conference speaker. He has been a Business Transformation Consultant at AgileThought for nearly two years now and previously was a Technical Advisor at InterContinental Hotel Groups.   In this episode, Dan and Sean explore the background and history behind DevOps, where they believe it is headed in the future, the enablers that help teams be most effective with DevOps, important mindsets to bring to DevOps, as well as both the challenges and benefits of DevOps not having a defined manifesto or framework.   Key Takeaways Challenges Sean sees the most without a manifesto in terms of defining good DevOps: It is harder to get education around it Lack of standardization Lots of interpretations of what DevOps is The benefits of DevOps not having a defined manifesto or framework: Freedom to create different frameworks around what works best for a customer or organization so it’s much more adaptive A supported culture of collaboration Able to adapt and grow more easily over the years Continuous learning Important mindsets to bring into DevOps: Focus on connecting the dots of Dev and Ops Work together as a team and articulate that to the business Get every stakeholder of the business involved Don’t do things in a vacuum Learn from every experience, good or bad Effectively debrief so you’re continuously improving and learning A strong culture with expectations Where Sean sees DevOps headed and where he thinks it should head: A possible name change as the name itself is limiting Not to think of DevOps in such a narrow way and instead, think of how to radiate it throughout the entire organization Be more careful about building silos in communities Move towards a model similar to ADAPT (which ties together Transformation, Agile, DevOps, and Product all into one executable transformation) DevSecOps and a greater culture of collaboration   Mentioned in this Episode: Sean Davis (LinkedIn) Agile Manifesto Patrick Debois (AKA the Godfather of DevOps) John Willis’ framework, CAMS DevOps Institute ITSM Academy Gene Kim’s ‘Three Ways’ Scrum DevSecOps Azure Terraform Xebialabs VSTS (Azure DevOps) Derek Wade Tom Gilmore, creator of ADAPT   Sean Davis’ Book Picks The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win, by Gene Kim, Kevin Behr, and George Spafford Reinventing Organizations, by Frederic Laloux   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!