Influencing Devops without Authority
summary
Shows a practical six-step influence without authority playbook (Cohen & Bradford) applied to DevOps: map allies, gather state of devops metrics (lead time, deployment frequency, change-fail rate, MTTR), trade value via hackathons and pipelines with baked-in guardrails, and recruit T-shaped teams. Cites industry data (elite performers triple from 2018 to 2019), describes building CI/CD (Jenkins, pipelines) and shipping a compliant pipeline that works, and tells one engineer-turned-CIO success as evidence.
AI-written summary · about
chapters (8)
- 0:00Start
- 12:28Goals and Priorities
- 14:02What Motivates People
- 14:48People Are Irrational
- 18:00When Can You Look for those Numbers in Order To Assess Your Organization
- 30:06Blinding Attitude
- 30:33Fear of Reaction
- 31:48Objections
related talks
01h 00mDoing DevOps Without Authority: How a ‘DevOps Engineer’ Can Help
01h 02mWe have DevOps. No one was fired. But what to do?!
34mDevOps Transformation from the C-Level point of view
01h 01m"Doing Devops" as a politically powerless developer
28mDevOPs Lessons for Frontend Developers
25mDevOps for Pointy-Haired Bosses
49m5 Steps to a DevOps Transformation
26mThe Timeless way of DevOps
