--- title: "Co-Ops: Enabling True Continuous Delivery with Cooperative Pipelines & Processes (Title Feedback Needed)" url: "https://pipelinedriven.org/article/co-ops-enabling-true-continuous-delivery-with-cooperative-pipelines-amp-processes-title-feedback-needed.md" canonical: "https://pipelinedriven.org/article/co-ops-enabling-true-continuous-delivery-with-cooperative-pipelines-amp-processes-title-feedback-needed" published: "2019-12-06T22:10:04.805000+00:00" updated: "2019-12-06T22:10:07.299000+00:00" tags: [] author: "Roy Osherove" description: "“Co-Ops” is a term that one of the attendees at a talk I was giving about cooperative pipelines came up with. I wish I knew his name. I asked him to email…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # Co-Ops: Enabling True Continuous Delivery with Cooperative Pipelines & Processes (Title Feedback Needed) 6 December 2019 · 1 min read · Roy Osherove “Co-Ops” is a term that one of the attendees at a talk I was giving about cooperative pipelines came up with. I wish I knew his name. I asked him to email me afterwards so I can credit him but he never did. Co-Ops describes the act of working with a cooperative pipeline: A Pipeline that every expertise contributes to: Dev, Test, Ops, Sec, Compliance etc.. a SINGLE Cooperative pipeline, with humans removed from tactical pipeline decision. I find it a really great naming scheme, and I think I’ll use it to title my book “Co-Ops: Enabling True Continuous Delivery with Cooperative Pipelines & Processes.” I’m still not fully “sold” on the full title. I fyou have ideas - I’d love to hear them. Your thoughts are welcome! --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/