BizDevOps
summary
Argues that DevOps must extend into business engagement by embedding business, development and ops together to avoid lost requirements and finger pointing; uses low‑code and cloud platforms (Power Apps, AppSheet, Excel/IFTTT examples) and a whole system in the room ritual. Runs a pressure cooker process: prepare, map domain, sketch, then build a one-week prototype (inventory system for a large brewer) that demonstrates value and clarifies whether to scale or stop.
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:17What is new
- 3:35New Technologies
- 4:35Business vs IT
- 9:18How we work
- 9:58Whole system in the room
- 10:48Bridge building
- 12:57Scrum demos
- 14:11Dive into domain
- 15:15Prototype
- 16:12Summary
- 22:40Questions
related talks
46mWork It Smarter, Dev It Better, Ship It Faster, Test It Stronger
30mBringing DevOps Success to Every App, Tool & Role in Your Org
28mDevOPs Lessons for Frontend Developers
04mHow It Happened
25mDeveloper Experience is central to DevOps success
54mDeveloper experience platforms
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation
37mDevOps for Java Developers (Or Maybe Against Them?!)