Improve your Product Roadmap with DevOps
summary
Uses system logs, monitoring and CI pages like Jenkins to turn noisy requests into roadmap decisions and concrete fixes: cluster of Harvard hackathon signups reveals onboarding friction and cutting fields raises activation, Netflix finds <1% external API traffic, and a Best Buy outage cuts store visits by 75% store traffic drop. Cites a three trillion dollar opportunity and 85 billion bad code loss, recommends monitor from within, TDD pairing yields a stable app and a tester at 25% time.
AI-written summary · about
chapters (16)
- 0:00Start
- 9:03Story Hell
- 11:17The Software Engineering Efficiency Opportunity
- 12:20Conway's Law
- 14:37Learning Organizations
- 18:29Escaping Vanity Metrics
- 23:07Visualize the Data
- 26:43The Job To Be Done
- 27:04Scrum Story
- 33:17Monitoring from within
- 33:51Tdd
- 38:00Team Manifesto
- 42:22Changing Priorities
- 43:56Leadership Prioritization of Projects and Tasks
- 45:35Equifax Breach
- 47:20Book Recommendations
related talks
01h 00mImprove your Product Roadmap with DevOps
30mA Story of DevOps Transformations
47mWhere the Security Rubber Meets the DevOps Road
28mBringing DevOps to Product
55mDevOps @Scale (Greek Tragedy in 3 Acts)
27mConcept to Code to Runtime - Simplify, Enable, Exploit
55mDevOps isn't just about developing
47mHow to win in software development with tighter feedback loops