Liatrio

Our collaboration with Ritchie Bros. was centered on empowering their engineering teams through immersive experiences in modern toolsets and practices. Due to their tremendous growth in a short period of time, Ritchie Bros. recognized the need to invest in their technology organization to establish a world class experience for their customers. We couldn't be more proud to contribute to this modernization effort in such a meaningful way! #DevOps #DeveloperExperience #CloudNative #PlatformEngineering #DevEx

There’s a lot to unpack in the 2024 #DORA Report, but here, I’m focusing on the Software Delivery Performance Levels. This report marks the first time in DORA's history that we’re seeing a data anomaly within these performance clusters. For many of us at Liatrio, this graphic sparked some of the most fascinating debates and internal discussions. So, what’s the anomaly? Typically, the Four Key Metrics (Deployment Frequency, Lead Time for Changes, Change Failure Rate, and Time to Restore Service) track together as teams progress from Low to Elite performance levels. But this year, high-performing teams show a higher Change Failure Rate than medium performers, despite improvements in Deployment Frequency. Why might this be happening? My hypothesis is that this gap reflects the growing adoption of microservices architectures and the learning curve of supporting cloud-native workloads in production. While reaching daily deployments is a milestone worth celebrating, it demands stronger investments in observability and SRE practices. Getting code to production faster doesn’t necessarily make it “easier” to support in production. Another possibility? AI-assisted code generation could be leading to more unchecked code, resulting in a slight decline in quality as deployment volume increases. One thing is clear: there’s a notable stability boost when moving from Low to Medium performance levels. This emphasizes the huge value of incremental improvement—even small steps can drive real results. At Liatrio, we’re deeply invested in DORA metrics because they often reinforce what we see in our engineering enablement work with clients. This data confirms our mission to equip teams with modern engineering practices, so they can adopt cloud technologies with confidence and efficiency. I’d love to hear your thoughts—does this data anomaly resonate with your team’s experience? What trends are you seeing in your performance clusters? #DORA2024 #EngineeringEnablement #DevOps #Observability #ContinuousImprovement #liatrio

This is awesome! 🔥 Our R&D team recently released and open-sourced our DORA Metrics Backstage Plugin. It’s now available in the Backstage from Spotify Plugin directory -> https://lnkd.in/dqHWctqF. 👏 At Liatrio, we believe the #DORA Core Model (https://dora.dev/research/), which contains the already well-known “four key metrics”, is an excellent guide to improving software delivery performance. Tracking these metrics specifically has proven to be a great way for software delivery organizations to see how they are performing today and chart a path to improving at a team-by-team and service-by-service basis. Ok that's great! But why did we build a #Backstage plugin? Glad you asked! Recently, many of the technology organizations we’ve worked with have been looking for better ways to track these metrics and make them visible to the teams who are impacted the most. Since our team has been working closely with Backstage as a centralized developer portal for some time, we thought it would be a great opportunity to create a unified view of each teams’ software delivery performance within the platform itself. Having these metrics handy allows the team to make more informed decisions, leading to faster and more reliable software delivery. While it’s not an exhaustive list of metrics, tracking change lead time, deployment frequency, change failure percentage, and failed deployment recovery time, gives clear insights into your development process. And by making these metrics available closer to development teams, they can set their own path to improving them. We’re always looking for ways to engage the community and we think there’s no better way than #OpenSource. So please give the plugin a try and let us know what you think! Reach out here on LinkedIn or on #GitHub if you have any questions or feedback! ----------- Liatrio DORA Metrics Plugin on GitHub: (for more detail and issues/contributing) ✅ https://lnkd.in/g4wAeAtX Don't forget to checkout the 2024 DORA Report: ✅ https://lnkd.in/dqiky6Cv Backstage Plugin Directory: (filter by category Observability to find it quickly) ✅ https://lnkd.in/dqHWctqF #DORAMetrics #Observability #SoftwareDelivery #DeveloperProductivity #DeveloperExperience #DeveloperPortal

Maybe a little FOMO is not such a bad thing? 😅 - Great conversation earlier today on the #DORA community call. Kevin M. Storer, Ph.D. gave a great summary presentation on AI adoption findings from the 2024 DORA Report and kicked off a lean coffee discussion on the topic. One of the points made in the report and on the call was that "competitive pressure", a nice way of saying FOMO, was a primary driver of AI adoption among the respondents. From the report: "Interview participants frequently linked the decision to adopt AI to competitive pressures and a need to keep up with industry standards for both organizations and developers, which are increasingly recognized to include proficiency with AI." But is that a bad thing? Maybe not! One of the key metrics called out: 👇 A 25% increase in AI adoption is associated with: - 7.5% increase in documentation quality - 3.4% increase in code quality - 3.1% increase in code review speed - 1.3% increase in approval speed - 1.8% decrease in code complexity. I think that even a small increase in any of these areas means that adoption of AI is worth a serious look for any team. So even if it was FOMO that got you moving, I think that's a win! 🚀 (If you haven't downloaded the DORA report - https://lnkd.in/gY5Nvyae)

All jokes aside, we hope everyone stays safe this Halloween! (Just not THAT SAFe.) #BeUnSAFe

We're thrilled that Alice J. was chosen to give a lightning talk at this year's #ArgoCon! ⚡ If you're there make sure to check out her talk on Tuesday, November 12!

Weekend reading: the 2024 DORA Report. https://lnkd.in/eZngCDP7 Dig into the impacts of AI, Platform Engineering, and Developer Experience. Looking forward to your feedback, reactions, and questions. #DORA #AI #GBGB

It’s time for enterprises to take back control of their platforms. Own the domain knowledge, understand the tools you’re operating and running, and ultimately break free from vendor lock-in. We’re giving our clients the power to build, scale, and innovate on their own terms. Learn more about how we’re doing it in our latest eBook 👉 https://lnkd.in/girNdUKN #PlatformFreedom #PlatformEngineering #VendorLockIn #OpenSource

The DORA 2024 Report is finally here! 👏 There’s so much we want to dig into here, and will do that over the next several weeks with some team deep dives in each area. But before we get into the weeds, we wanted to give some fast-feedback review of some themes that stood out. This year, as always, the report hits on some of the hot-topics and trends. The attention to software delivery performance is a headliner, but the report does a great job surfacing the impact of things we’re all talking about the most. Some of the big areas of focus are AI, Platform Engineering, and Developer Experience. Quick takeaways on those themes: ➡ Software Delivery Performance - A big takeaway that the authors of the DORA report want you to come away with is to emphasize continuous improvement rather than merely achieving elite performance levels. This is battling the urge to “score” or level teams based on the same metrics across the board. Teams are different and what is “elite” vs. “high-performing” may not be transferable. ➡ Artificial Intelligence - While AI brings productivity gains and improves code quality (the report has some good detail here), it (strangely) seems to hurt overall software delivery performance by introducing instability in later stages of the SDLC. We think this is really interesting and will be digging in deep here as we have some great insights into why this is and will be sharing our thoughts in at least one follow-up post. ➡ Platform Engineering - In the report, Internal development platforms (IDPs like Backstage) can help boost developer productivity, particularly in larger firms - but not without careful/intentional implementation. We believe this means treating platforms with a specific product mindset/focus. Great area to discuss further here as we get into the evolution of DevOps. ➡ Developer Experience (and User-Centricity) - Driving a user-centric approach shows to greatly benefit product quality and team performance, suggesting that understanding user needs may outweigh the necessity for high software delivery performance. This one we may disagree with! We’re still discussing why there may be tradeoffs here and want to spend more time reviewing the report in detail. More to come here for sure. 🚧 That was just a quick review of some of the themes so we may "evolve" some perspectives as we spend more time in the report. All of the detail around transformational leadership, robust feedback loops, and experimentation are going to be themes of future deep dives. Looking forward to having some engaging discussions! 🚀 Make sure you head over and download your copy! 👉 https://lnkd.in/gM5r2SmD #DORA #DORAReport #TechTrends #SoftwareDevelopment #PlatformEngineering #AI #DevOps

As sponsors of this year’s DORA report, we’re excited to announce the 2024 report has been released! Packed with research and insights, this report explores the key factors shaping the future of software development. Stay tuned over the next couple weeks for more in-depth insights from our page and the Liatrio team about what the findings mean for enterprises and how we’re implementing them with clients. Download it today 👉  https://lnkd.in/gM5r2SmD #DORA #SoftwareDevelopment #TechTrends #AI #DevEx #PlatformEngineering