#DataDrivenDevops
summary
Claims that cross-pillar metrics from dev QA and ops get integrated into actionable decisions with concrete results: measuring test‑environment utilization reveals engineers hoarding environments and a small auto‑return tool cuts average utilization, adding spare capacity; a JIRA “test suite stability” bug type and fixes drive down flaky tests over months; CI + source control + Artifactory dashboards surface rising build time and storage needs; machine-driven canary deploys detect regressions and execute canary rollback <1 minute using SignalFx and JFrog Mission Control.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:36Optimism
- 3:53Consequences
- 7:07Metrics
- 10:19DevOps
- 13:10Why we measure
- 16:23Examples
- 23:26Tips Tricks
- 28:14Continuous Delivery
- 34:19DataDriven Life
related talks
34m#DataDrivenDevOps
42mData-Driven DevOps
47mWithout Data, you're just another Person with Opinions
42mData Driven DevOps
25mImplementing Metrics-Driven DevOps: Why and How
59mDevSecOps Productivity Metrics and Tools
37mCI/CD Observability, Metrics and DORA: Shifting Left and Cleaning Up!
33mMeasuring Developer Efficiency in DevOps: Key Questions, Metrics, Best Practices
