Agile - DevOps
Technology value stream
- "converting a business hypothesis into a technology-enabled service that delivers value to the customer" - work start as an item is added to backlog - item is converted into a user story with additional specs - user story is then converted into code - code is then checked into version control repo where changes are integrated and tested - once changes are deployed, deployment cannot cause chaos or disruptions
devops approach can be remarkable for those who implement it well
- 46 times more frequent code deployments
Myths about DevOps that are incorrect
- DevOps is only for startups - DevOps replaces Agile - DevOps is incompatible with ITIL - DevOps is incompatible with info sec and compliance - DevOps means eliminating IT Operations (NoOps) - DevOps is just infrastructure as code (automation) - DevOps is only for open source software
Principles of continual learning and experimentation
- Enabling organizational learning and a safety culture, reinforced by leaders - Institutionalize the improvement of daily work - Transform local discoveries into global improvements - Increase resilience patterns into daily work (pushing for stress tests and fire drills)
DevOps wants to decrease both lead time and process time
- Lead time: ticket created -> work started -> work completed - Process time: work started -> work completed - Lead time can take months but we want to reduce as much as possible - developers need to receive fast feedback - continuously checking small batches of work, with automated validation process will help
Principles of Feedback
- See problems as the occur - Swarm and solve problems to build new knowledge - Keep pushing quality closer to the source (especially through automation) - Enable optimizing for downstream work centers (minimizing their preparation to work on their tasks)
What is DevOps?
- integration of development and it operations (plus qa and infosec) to maximize the workflow and increase high-quality productivity in software solutions - most organizations development and it operations not only are separated but can even have an adversarial relationship, including "technical debt" - devops attempts to fix that and has become an important aspect of it management
Principles of Flow
- make work visible (with a board) - limit WIP - reduce batch sizes (full cycle vs. many in phase) - reduce number of handoffs (through automation or multi disciplinary teams) - continually identify and elevate constraints - eliminate waste in value stream
DevOps has evolved over a long time
- natural evolution, perhaps brought out of necessity - relies on manufacturing principles that have been around for many years - fundamental belief that IT can be managed as a factory
