InfoQ Homepage Metrics Content on InfoQ
-
/articles/ci-cd-observability/en/smallimage/logo-1679470476672.jpg)
Improving CI/CD Pipelines through Observability
CI/CD pipelines are a vital addition to any workflow, but they can be further improved by the selective addition of observability. This article covers what data to monitor, which metrics to track, and how to best visualize the collected data.
-
/articles/Skyscanner-metrics-culture-improvement/en/smallimage/logo-1678141795806.jpg)
How Skyscanner Embedded a Team Metrics Culture for Continuous Improvement
This article explains why Skyscanner decided not just to deploy a tool, but to think about this as changing their engineering management culture to being one that values and utilises metrics to drive greater improvement at scale. It shows how they evaluated tools to find one that would enable their teams and reinforce the cultural change that was the fundamental goal of this exercise.
-
/articles/incident-metrics-void/en/smallimage/past-simple-incident-metrics-courtney-nash-VOID-small-1676021060277.jpg)
Moving Past Simple Incident Metrics: Courtney Nash on the VOID
The Verica Open Incident Database (VOID) is assembling publically available software-related incident reports. InfoQ talks with Courtney Nash about their recent findings including how MTT* metrics may not be beneficial, the average time to incident resolution, and the importance of studying near-miss reports.
-
/articles/process-data-find-more-bugs/en/smallimage/logo-1674649351750.jpg)
How to Use Your Existing Software Development Process Data to Find More Bugs in Less Time
This article presents better solutions that employ data from the system under test and the tests themselves to optimize testing efforts. This allows teams to find more bugs (by making sure that bug-dense areas are tested) in less time (by reducing the executions of tests that are very unlikely to detect bugs).
-
/articles/metrics-quality-software/en/smallimage/finding-adequate-metrics-for-process-quality-in-software-development-small-1673953064694.jpg)
Finding Adequate Metrics for Outer, Inner, and Process Quality in Software Development
Implementing a feature can be measured. Quality is harder to measure. This article explores how to balance improving quality and adding new features. It dives into different domains of quality: Outer quality which is owned by the product people (e.g. product owners, testers), inner quality owned by the developers, and process quality owned by managers.
-
/articles/team-level-metrics-matter/en/smallimage/LOGO-1673637433912.jpg)
Why Team-Level Metrics Matter in Software Engineering
In a world where everything can have perspective, context and data, it doesn’t make sense to limit that to just part of your software development process. The DORA metrics can provide insight into the health of your development environment, where value is being delivered and opportunities for improvement. Metrics must be used with careful insight to separate the signal from the noise.
-
/articles/monitor-digital-experience-feature-effectiveness/en/smallimage/monitoring-digital-experience-to-determine-feature-effectiveness-small-1666951981148.jpg)
Are They Really Using It? Monitoring Digital Experience to Determine Feature Effectiveness
This article reflects on the challenges of determining user experience and effectiveness and how modern techniques such as Real User Monitoring and Application Performance Monitoring can determine the true effectiveness of features. It includes stories from banking to show which measures can help agile teams determine not only if features are being used, but diagnose other common issues too.
-
/articles/analyzing-incident-data/en/smallimage/logo-1656066636167.jpg)
Analyzing Incident Data across Organizations: Courtney Nash on the VOID
The Verica Open Incident Database (VOID) is assembling publically available software-related incident reports. InfoQ talks with Courtney Nash on their recent findings including how MTT* metrics may not be beneficial, the average time to incident resolution, and the importance of studying near-miss reports.
-
/articles/mtt-metrics-incident-response/en/smallimage/logo-1647371343575.jpg)
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.
-
/articles/beyond-monitoring-change-intelligence/en/smallimage/logo-1642766732099.jpg)
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.
-
/articles/measure-outcomes-not-outputs/en/smallimage/measure-outcomes-not-outputs-small-1639490155013.jpg)
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.
-
/articles/metrics-analytics-recover-problem/en/smallimage/applying-software-delivery-metrics-and-analytics-to-recover-a-problem-project-small-1635761918128.jpg)
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.