DevOps notes
Recently I’ve been reeding books:
- The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win
- The Unicorn Project: A Novel about Developers, Digital Disruption, and Thriving in the Age of Data
- The DevOps Handbook
Four Types of Work
- Business Projects: Customers are paying us; managed
- Internal Projects: Lots of inter-dependant tasks; often not managed
- Operational Change: Little tasks
- Unplanned Work: Highest priority, disruptive
| Flow item | Delivers | Is pulled by | Description | Example artifacts |
|---|---|---|---|---|
| Feature | New business value | Consumers | New value added to drive a business result | Epic, user story, requirement |
| Defect | Quality | Consumers | Fixes for quality problems that affect the customer experience | Bug, problem, incident, ITIL change |
| Risk | Security, governance, compliance | Security | Work to address security, privacy, and compliance exposures | Vulnerability, regulatory requirement |
| Dept | Removal of impediments to future delivery | Architects | Improvement of the software and operational architecture | API addition, refactoring, infrastructure automation |
| Visible | Invisible | |
|---|---|---|
| Positive value | Feature | Architecture |
| Negative value | Defect | Technical dept |
The three ways of DevOps
- Systems thinking: work flowing from left to right as fast possible
- Amplify feedback loops: increasing the feedback loops from right to left
- Culture of continual experimentation and learning: is encouraged
The Five Ideals
- Locality and Simplicity: You should not depend on work done by others
- Focus, Flow, and Joy: You should be able to concentrate on your work
- Improvement of Daily Work: Pay down technical dept
- Psychological Safety: No fear to talk
- Customer Focus: core vs. context
Written on October 28, 2020