BizOps and you
summary
Claim: putting sales/marketing/finance into DevOps decisions raises impact by changing what gets measured and how incidents get handled. Describes monitoring strategy, post-mortems, chatops and gives specifics: migration choice between GitHub and internal GitLab because of client contract clauses; an A/B email tweak that nets 2.6% lift in a day; post-mortems that convert 99th‑percentile alerts into actual users affected and revenue lost. Recommends collecting broad signals, correlating them, and involving business people continuously.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:44Definition of DevOps
- 2:05What is DevOps
- 2:44Your job
- 3:11Technology without business
- 4:47Support business
- 6:30I love Dilbert
- 8:03Every decision should support our businesses
- 8:13You do not understand how business works
- 10:19Business doesnt understand you
- 12:01DevOps come in action
- 12:23Sometimes its difficult
- 12:36Assume
- 13:28Requirements
- 13:52People
- 16:29Perspective
- 16:45Postmortems
- 17:58Visibility
- 20:18Collaboration
related talks
28mBizOps and you
47mDevOps is for Product Engineers, too.
05mDevOps and incident management: A recipe for success
22mDevOps in Regulated Industries: What to do when Internal Audit says ‘No!’
33mOperations: the last Mile for DevOps
16mDevOps and the Bottom Line
43mDevOps – when doing the right thing hurts!
25mDevOps for Pointy-Haired Bosses