As organizations begin to work on numerous services and components many are faced with a new set of challenges.  Adding to these challenges is the ever increasing remote and distributed workforce.  This places a significant operational and tooling overhead on standard development teams. Each team needs its own pipeline, monitoring-alerting, on-call staff, etc.  It is not enough for teams to be agile in coding and systems, teams need to understand how a change can affect a distributed system.  With new service frameworks focusing on community pipelines, enhanced collaboration, and team ownership, sanity can exist.  Pipeline as a Service can help force organizations transformation into Community DevOps.

In this session we will discuss how Community DevOps can enable teams to mange the complexity of modern development from ideation to production.  We will discuss how pipeline as a service provides the right balance of ownership from a single team to an enterprise, the technical components and how to avoid common pitfalls.