Correlations between DevOps and Holacracy
summary
Claims that Holacracy accelerates DevOps outcomes through concrete practices: removal of job titles (Lego standardizes on continuous delivery engineer), elimination of change approval boards (Lego runs peer-based change reviews instead of up to seven or eight CAB layers), use of GlassFrog and the GitHub Holacracy Constitution to map roles, and toolchain hygiene with Jenkins/Puppet and Sonatype. Finance shifts from 12‑month budgeting toward quarterly rolling funding (one bank reports moving from 4% to 90% of strategic projects to agile funding).
AI-written summary · about
chapters (12)
- 0:00Intro
- 1:13Fanatical about making life on earth fantastic.
- 9:31Correlations?
- 11:45No job titles, focus on roles
- 14:07Flattened hierarchies and distributed authority
- 17:53Peer based reviews
- 19:04Amplified feedback loops / processing tensions
- 20:07Continuous funding
- 25:31Incremental, iterative improvement
- 30:02Transparency
- 32:17Automation
- 37:31In Conclusion
related talks
56mTesting Through Monitoring or Holacracy in Practice
41mSelf-organizing development at Springest with Holacracy
43mScrum and Holacracy – complement or overhead?
41mA Holistic Approach to DevOps
09mexplains DevOps Culture
21mScaled Agile DevOps
27mDevOps in a Windows (Enterprise) World
34mYou only have to change one thing to do the DevOps