Which two measures together BEST show shared success across technology teams?

Shared success across technology teams in DevOps is best demonstrated by balancing throughput and stability across the software delivery lifecycle. Historically, Development teams focused primarily on throughput while Operations teams focused strictly on system stability, creating opposing incentives and functional silos. DevOps aligns these disparate teams around shared enterprise goals by evaluating overall technology performance across both dimensions simultaneously. High-performing DevOps organizations achieve high throughput alongside high system stability, demonstrating that delivery speed and operational reliability are mutually reinforcing rather than mutually exclusive. Together, throughput and stability provide the most accurate, holistic representation of shared success across technology teams.

B. Deployment frequency and change lead time measure only throughput, failing to evaluate system stability, quality, or operational risk.
C. Mean Time to Repair and change failure rate measure only stability, completely ignoring delivery speed and throughput performance.
D. Employee retention and Net Promoter Score measure organizational culture and customer satisfaction, not core technology delivery performance.

Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps. IT Revolution Press. Chapter 2: Measuring Performance.

Forsgren, N., & Kersten, M. (2018). "DevOps metrics: Your indispensable guide to heavy-hitting metrics." IEEE Software, 35(5), 86-90. DOI: https://doi.org/10.1109/MS.2018.3571247

PeopleCert DevOps Foundation Official Syllabus, Section: Key Performance Metrics for Business and IT.