Roy is the author of "The Art of Unit Testing", "Elastic Leadership" and the upcoming "Pipeline Driven" books. He is an independent consultant working across Europe coaching about TDD, Leadership, Continuous Delivery & DevOps. You can learn more at osherove.com
unfold_lessunfold_more The Pipeline Driven Organization — Enabling True Continuous Delivery at Scale
- Why DevOps Adoptions fail at large enterprises
- What does "pipeline driven" mean and how it enables continuous delivery
- Getting Dev, Test, Security Ops and Compliance on board
- Skills needed in continuous delivery based organization
A Pipeline Driven Organization is operating around the idea that automated pipelines make the important IT decisions such as: - When is it OK to deploy a new version? - Is a feature working? - When and how to deploy a new environment - When to rollback (or forward) a new version - Are we compliant and secure? - Is the code releasable? - Are the infrastructure changes OK? In traditional organizations, even though automated pipelines may exist, they do not make the important & continuous IT decisions. Humans do. In a pipeline driven organization, experts from various categories of work spend much of their time teaching and learning from other people, and teaching the pipelines how to make proper decisions (using automated specialized tests). In this way they can trust the pipeline enough to let it make the decisions instead
- Test-First Mechanics and their reasons
- TDD is not about testing. It is about Development.
- Design ideas and refactoring.