InfoQ Homepage Metrics Content on InfoQ
-
How to Best Use MTT* Metrics to Optimize Your Incident Response
Selecting the correct MTT* metric to improve your incident response is important. If the wrong metric is chosen, the improvements may get lost in the noise of a multivariable equation. This article reviews the various MTT* metrics available and discusses the best scenarios for selecting each one.
-
Why Change Intelligence is Necessary to Effectively Troubleshoot Modern Applications
Change Intelligence is often a missing component in incident management. Successfully correlating monitoring and observability data to arrive allows engineers to arrive at the root cause more rapidly. Telemetry provides the building blocks that enable change intelligence to identify and map the root cause, based on changes in the system and their broader impact.
-
Measure Outcomes, Not Outputs: Software Development in Today’s Remote Work World
Today’s remote work world calls for a closer look at how to measure software developer productivity. Currently, there is no standard metric and widely used methods are flawed. The author describes how they successfully lead 500+ remote software developers by measuring outcomes, rather than outputs in order to produce the ideal balance between speed and quality code development.
-
Applying Software Delivery Metrics and Analytics to Recover a Problem Project
Problem software delivery projects can be recovered mid-flight if Value Stream Management (VSM) analytics are used in a forensic way to uncover the root-cause of the issues. The root-cause metrics areas considered include: People Availability; Team Stress; Backlog Health; Sprint Accuracy; Process Efficiency; Story Management; and Defect Gen. A root-cause RAG reports shows key mitigations.
-
Speed, Efficiency, and Value: Using Empiricism to Achieve Business Agility
Customers seek solutions that improve their outcomes, and organizations don’t know what will achieve this until they deliver something to them, measure the results, and adapt accordingly. Doing so repeatedly, frequently, and with the smallest investment to achieve the greatest amount of feedback, is the essence of organizational agility. This is key to success in today's complex world.
-
Applying Genetic Engineering to Your Organization Culture
Common barriers to transformation value remain people, mindset, and organizational culture; they are so significant that they can halt any transformation from achieving meaningful delivery capabilities. Behavioral mechanisms can work as a sophisticated DNA blueprint that directs actions. This article explores mechanisms for DNA manipulation to apply the concepts in the organizational environment.
-
Improving Speed and Stability of Software Delivery Simultaneously at Siemens Healthineers
In this article, we focus on the software delivery process at Siemens Healthineers Digital Health. The process is subject to strict regulations valid in the medical industry. We show our journey of transforming the process towards speed and stability. Both measures improved at the same time during the transformation, confirming research from the “Accelerate” book.
-
A Journey in Test Engineering Leadership: Applying Session-Based Test Management
This article shows how modifying Session-based Test Management to our context helped us gain more visibility into our testing. Having a structured yet flexible approach to test management allowed us to make better, more timely decisions about the testing, and gave us more opportunities to influence quality decisions earlier in the process.
-
Lessons Learned about Developer Experience from the Platform Adoption Metrics @ Naranja
With the intent of improving the product-based approach to their internal platform, Naranja has implemented an automated metrics solution that captures essential figures that describe how their teams are doing in terms of adoption, up-to-dateness and applicability of the solutions their Developer Experience creates. This enables better collaboration on their technology roadmap.
-
Reawakening Agile with OKRs?
Corporate agile often represents an improvement over what went before but falls short on delivering the high performance management wants and quality engineering environment developers dream of. The backlog becomes tyranny. Could OKRs - objectives and key results - reawaken the radical side of agile? Or do OKRs represent a return to command and control?
-
Increasing Developer Effectiveness by Optimizing Feedback Loops
We can think of engineering as a series of feedback loops: simple tasks that developers do and then validate to get feedback, which might be by a colleague, a system (i.e. an automation) or an end user. Using a framework of feedback loops we have a way of measuring and prioritizing the improvements we need to do to optimize developer effectiveness.
-
Key Metrics to Track and Drive Your Agile Devops Maturity
To promote DevOps and Agile process improvement, a meaningful set of metrics should be tracked. In this article we will discuss which metrics are appropriate based on the stage of the culture change. Coupling these metrics with strong support from leadership will ensure the best improvements in team measures such as cycle time, deployment frequency, and software quality.