There's telemetry for engineering systems, and then there's telemetry for engineering teams. They're not the same. Code is standardized, more or less. But every team is unique — the metrics of a healthy team can look completely different from organization to organization. What's missing from most "productivity" conversations (and most productivity data) is context of what's actually happening within your organization. For effective teams, that holistic context is critical. Uplevel VP Product Christina Forney explains why: https://lnkd.in/gX9CFXgT #developerproductivity #engineeringperformance #engineeringleadership
Uplevel’s Post
More Relevant Posts
-
Engineering Manager | Mobile, SuperApp, MiniApp & Backend Development | Specialising in MicroService & GenAI Applications | Driving Innovation in GenAI Apps
To improve your engineering efficiency quickly and continuously, you must know 𝗗𝗢𝗥𝗔 𝗠𝗲𝘁𝗿𝗶𝗰𝘀. I have been using this for the past few months to measure the software delivery velocity and throughput of my team, and I must say instead me loving this, the developers love this metric as it reflects back their real scenario without any filters. 𝗔 𝗯𝗶𝘁 𝗼𝗳 𝗯𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 DORA metrics come from an organization called DevOps Research and Assessment. This was a team put together by Google to survey thousands of development teams across multiple industries to try to understand what makes a high-performing team is different from a low-performing team. What they ended up settling on are these four metrics 🚀 Deployment Frequency 🚀 ⏳ Change Lead Time ⏳ 📉 Change Failure Rate 📉 📈 Mean Time to Recovery 📈 This information can also flag if engineers are losing engagement, highlight high and low performers and help companies avoid resorting to quick fixes that aren’t sustainable. Great use case if you run a team across multiple locations like me. Quick Explanatory: https://ow.ly/BHjq50Pz261 In-Depth: https://ow.ly/Ciar50Pz262 Image Credits: https://ow.ly/33Uw50Pz263 💬 Please write in the comment section below about your experiences. #EngineeringEfficiency #SoftwareDelivery #TeamPerformance #HighPerformingTeams #MetricsThatMatter
To view or add a comment, sign in
-
DORA metrics have been hailed as vital for measuring developer enablement success 👩💻📉 But are you using it correctly? 🤔 Google Says you might not be. Nocnica Mellifera in her recent article shares ways how DORA metrics can be misused. Below are key takeaways from this piece. Hope it helps 👇 🔶 Five key DORA metrics are ➡️ Deployment frequency: How often do you successfully release to production? ➡️ Lead time for changes: How long does it take a commitment to get into production? ➡️ Change failure rate: What percentage of deployments cause failures in production? ➡️ Time to restore service: How quickly can your organization recover from production failures? ➡️ Reliability: How do latency, performance, and scalability impact operational performance? 🔶 High-stakes vs. Low-stakes metrics ➡️ Low-stakes metrics are beneficial when kept within the team. They foster improvement and accountability. ➡️ High-stakes metrics ensure adherence to expectations rather than driving improvement. 🔶 Ways that DORA metrics are misused ➡️ Narrow focus on performance metrics over business goals. This results in neglecting other critical aspects such as organizational performance, team dynamics, reliability, burnout, and job satisfaction. ➡️ Comparing teams rather than assessing improvement over time. Each software team operates in a unique environment. ➡️ Misinterpretation and misapplication, leading to superficial improvements of metrics rather than genuine improvements in software delivery or team well-being. ➡️ Focusing solely on the quantitative aspects of DORA metrics and neglecting human factors like burnout and job satisfaction. These aspects are crucial for a sustainable and effective work environment. ➡️ Cultural misalignment if leadership fails to embody metric principles. Since DORA metrics are not just numbers, they represent a culture. Kudos to Nočnica Mellifera for addressing this vital topic with clarity and depth. Extremely helpful! 🙏 #developerexperience #engineeringmanagement #engineeringleadership #dorametrics #metricsmatter
The Wrong Way to Use DORA Metrics
https://thenewstack.io
To view or add a comment, sign in
-
🚀 Platform Engineering: Strength of modern Engineering teams 💪 As software development progresses, so does the complexity. We've seen remarkable advancements, yet there's still much ground to cover. The challenge lies in navigating through diverse environments and organizational overheads, hindering effective strategies. As per research conducted by Gartner, nearly 80% of sizeable engineering teams will institute platform engineering teams within their structure by 2026. Platform Engineering serves as the cohesive force, pulling together everything to streamline operations. By establishing a golden path for developers, these teams enhance productivity and accelerate innovation. Successful organizations are recognizing the importance of platform teams in overcoming hurdles and fostering agility. It's about creating a structured pathway where developers can thrive and innovations can flourish. Read more on our blog: https://buff.ly/49KkJzv #PlatformEngineering #DevOps #Productivity #Agility
To view or add a comment, sign in
-
Are you leading your dev team in the wrong direction? If you’re hyper-focused on one metric – speed – you can easily neglect all the others, including direction. ❌ This happens to engineering teams all the time: Using the wrong metrics, a limited set of metrics, or metrics without context. If you’re relying on DORA Metrics alone, it’s like only paying attention to the speedometer when you’re driving. You still need a map—something to benchmark the success of your team against—or else it’s easy to get lost. Metrics tell you where you are, but benchmarks give you a map that shows you where you can go. That’s why in 2022, LinearB studied ~2,000 dev teams and created their engineering benchmarks report, building on the seminal DORA research to provide engineering leaders with clear guidance on where they can improve. 📊 Although learning where you’re underperforming is not a pleasant experience, it's ultimately for the better. Benchmarks are valuable precisely because they reveal often-overlooked areas for improvement—it’s hard to self-evaluate objectively. Some engineering leaders have also expressed concerns that benchmarks would take away their decision-making power. But benchmarks don’t tell you where to go. They’re a map that tells you where you can go. Ultimately, it’s up to leaders and their teams to decide what route is best for them. While direction can come from the top-down, actual improvement needs to come from the bottom-up. Individual engineers have to make changes in their workflows to drive improvement at the team level. This means that engineering leaders should focus on building systems that empower developers to take the wheel and drive improvement in their processes to accomplish the team’s goals. DORA Metrics were a huge step forward for engineering teams, ushering in the era of data-driven engineering by providing a small set of clear metrics. Nine years later, the data is becoming clear. If we: 🔎 Track key metrics like DORA 📊 Provide context with engineering benchmarks 🔄 Leverage automation to unstick devs’ workflows 🏆 You build high-performing dev teams If you build a high-performing dev team, and give them the right map, you’ll deliver better quality software, faster—software that’s valuable to your customers. Learn more in our newest blog from co-host Conor Bronsdon in the comments below 👇 #Metrics #Data #EngineeringLeadership
To view or add a comment, sign in
-
Measuring developer productivity is a double-edged sword ⚔ Done right, it can improve visibility, predictability, and innovation. Done wrong, it can suffocate creativity and destroy morale. Read more on how to strike the right balance 👇 https://lnkd.in/dhkEd8gN #productivity #developer #softwaredeveloper #softwareengineer #CTO #software
When Developer Productivity Measurement Backfires (and How to Fix It)
middlewarehq.com
To view or add a comment, sign in
-
🚀 Exciting Insights into Developer Productivity Teams! 📈 Just came across a fascinating article by Abi Noda on the allocation of engineering headcount towards developer productivity teams. It's a must-read for anyone in the tech and software engineering industry! Key Takeaways: - 📊 On average, companies with <1000 engineers allocate about 18.9% of their headcount to centralized productivity teams. - 🌟 Larger organizations tend to invest a smaller percentage, but the absolute number remains significant. - 🤔 Insights from industry leaders like Will Larson (CTO at Carta) and Rajeev Rajan (CTO at Atlassian) provide valuable strategies for enhancing developer productivity. Why It Matters: Understanding how to effectively allocate resources towards developer productivity is crucial for innovation and efficiency in tech. The article sheds light on the balance between centralized and localized efforts in improving developer experiences. Looking Ahead: With a growing focus on DevEx initiatives, we can expect an increase in investments towards productivity teams. 🔗 Check out the full article for deeper insights: https://lnkd.in/egQeBKmQ #DeveloperProductivity #EngineeringManagement #TechInsights #Innovation #SoftwareEngineering
Companies Allocate 19% of Engineering Headcount Toward Developer Productivity Teams
newsletter.getdx.com
To view or add a comment, sign in
-
IoT Expert | Helping Businesses with Expert IT Outsourcing | IoT ,Cloud DevOps & MERN Stack Specialist team | Co-Founder at ScroBits
The Future is Platform Engineering - Unveiling the Secret Sauce of Developer Productivity 🚀 As I was winding down yesterday, contemplating the whirlwind of projects and deadlines, I stumbled upon an enlightening blog post by InfraCloud on Platform Engineering. It got me thinking about how this concept is revolutionizing the way we approach software development. 🌟 The Need for Platform Engineering In the last decade, the DevOps movement brought development and operations teams closer than ever. But it also led to an explosion of tools and technologies, increasing the cognitive load on engineers. Enter Platform Engineering - a discipline designed to empower developers by reducing this load, allowing them to focus on what they do best: coding. 🛠️ What is a Platform? A platform is essentially an interface that abstracts away the complexities of underlying infrastructure technologies. It provides a unified set of tools and processes, enabling better collaboration and faster time-to-market. 📚 Key Principles 1️⃣ Standardization: Promotes consistency and efficiency across the development process. 2️⃣ Automation: Reduces time-consuming tasks and human errors. 3️⃣ Abstraction: Shields developers from the complexities of the underlying infrastructure. 🔄 Platform as a Product The game-changer here is treating the platform as a product. This mindset focuses on user experience, iterative improvement, and aligning the platform with larger business goals. 🔍 When Do You Need a Platform? - Increased application complexity - Frequent releases - Resource optimization - Inconsistent environments - Security & compliance needs 🛠️ Popular Tools - Backstage - Kratix - Crossplane - Humanitec - Port 🌟 Final Thoughts Platform Engineering is not just a trend; it's the future. It's about optimizing developer experience and boosting productivity. If you haven't considered it yet, now might be the time. For a deeper dive, check out the InfraCloud blog: https://lnkd.in/dvzH9n53 Would love to hear your thoughts on this! Are you already on the Platform Engineering train? 🚂 Scrobits Technologies Digvijay Jadhav Kunal Sarpatil #PlatformEngineering #DevOps #SoftwareDevelopment #Productivity #Innovation
To view or add a comment, sign in
-
Measuring performance is complex. Engineering managers must understand how individual contributors are performing and how the team combines to produce code. Add to that the problem that engineering managers lose visibility as products become more complex and organizations grow. DORA metrics were created at Google to help solve these problems. Let’s take a closer look at the four DORA metrics and how they can help your organization. https://lnkd.in/dsWiuANE #teamperformance #productivity #softwaredevelopment #dorametrics
A Guide to DORA Metrics and Accelerating Software Delivery
blog.codacy.com
To view or add a comment, sign in
-
Insightful blog on the transformative power of platform engineering from a business perspective. Rob Zuber, a seasoned founder and CTO, delves into how this approach drives customer-centricity, agility, and early-stage development, offering invaluable guidance for businesses aiming to thrive in today's dynamic tech environment. #platformengineering
Elevate Your Business with Platform Engineering - Spiceworks
spiceworks.com
To view or add a comment, sign in
-
Gartner Software Engineering Leader, Digital champion, Public speaker, Product manager, Innovator, Bridge to Asia and China, Dogs lover, Photographer, Golfer, Cancer Survivor
Is your Software Engineering setup to Accelerate Digital for Future-Ready Business yet? Do you know how to prioritize what to accelerate? where to invest? and keep in digital momentum? How to improve better outcomes and employee experience, productivity, attracting and retaining customers 3 Ways to Make Your Software Engineering Team 50% More Effective - Empower teams to shape standards - Promote critical skills - Practice servant leadership https://lnkd.in/g9Jw7Jm3 #Gartner
3 Ways to Make Your Software Engineering Strategu More Effective
gartner.com
To view or add a comment, sign in
2,172 followers