culture & devops
this book highlighted to me, the importance of culture in order for an organisation’s devops efforts to succeed.
culture can be a bit of a buzzword, and is inherently a subjective term, but it is ‘quantified’ well in the book.
Management
Related
- Book notes by Charles Flatt
Summarised by Gijs Meijer & Marcin Pakulnicki
3 things you want to iterate & improve on, for more effective software delivery:
- Flow
- Feedback
- Culture
Flow
- fast from dev to prod
- trunk based dev
- ci
- immutable, containerized build - enables fast rollback, and maybe other benefits, that I’m not yet aware of
Feedback (everything after you’ve deployed the code)
- fully automated testing
- monitoring, alerting, logging
- code scan, OWASP check
- shift left of risk
Culture
- eng culture
- learning organization (Google 20% mastery time)
- post mortems
How do the authors define, quantify, and measure culture?
on Developer Velocity
Borrowing from Will Larson’s summary in Elegant Puzzle, velocity is measured by:
- Delivery Lead time - time from creation of code, to its use in production
- Deployment frequency
- Change fail rate
- Time to restore service