Source: London Continuous Delivery

July 2020 Meetup

Join us for an evening of great discussions & talks.

Zoom link will be shared closer to the event date.

More detailed plan will be shared shortly.

Talk 1: Continuous money by Allan Kelly

Continuous delivery has taken us past big bang - we can, and do, deliver better than one off big releases. But while techies have moved forward management practices remain rooted in start-stop, start again-stop(late, again) world. There is friction when technical practices and management practices don't agree.

Nowhere is this friction greater than in the way funding works. If we are to unlearn project funding we need an alternative model to put in its place. In this presentation Allan Kelly will outline that model. A model which uses minimally viable teams and good old-fashioned portfolio management to redesign funding and management.

Allan Kelly helps software professionals, teams and enterprises enhance agility in a digital world. Through direct advice, consulting, training and books he applies his wide experience to the challenges faced in software development. His novel, and sometimes radical, ideas create software development environments were people can thrive.

He is the author of seven books including his latest book "The Art of Agile Product Ownership." He has pioneered techniques such as Value Poker, Time-Value Profiles and Retrospective Dialogue Sheets. His blog is at and on Twitter he is @allankellynet.

Talk 2: Avoiding the CI/CD Monolith with Team Design & Evolution by Manuel Pais

We often talk about monoliths at the application and database level. However, there are many other manifestations: monolithic tooling, monolithic infrastructure, monolithic releases, monolithic testing, and even monolithic thinking.

In my experience, more than legacy technology or architecture, the emergence of monoliths often comes down to a lack of purposeful team design and evolution. Conway’s Law - the mirroring effect between team structures and dependencies and the resulting system design - is no stranger to CI/CD. Once we acknowledge the socio-technical nature of software delivery, we consequently recognize the need for a team-centric, not tool-centric, approach for sustainable CI/CD.

We start asking questions like: should every application team own and maintain their own instances and flavors of the CI/CD tooling (since it’s all codifiable now, right)? Or do we need a CI/CD team to handle the tooling and infrastructure for everyone else in the org so teams only have to worry about their own pipelines? Or something in between, like a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs?

Just like we are advancing our tools to become easier to install, run and update, we also need to think about clarifying team interactions and responsibility boundaries for effective ownership and evolution of both the CI/CD system (it’s actually a product) and the application pipelines.

Key takeaways​:
1. Moving to fast, distributed, and reliable CI/CD systems is not just a matter of better tooling and scalable infrastructure, but also clearer team design and responsibilities.

2. With “everything-as-code” for CI/CD, application teams can be empowered to own their CI/CD chains if they wish. But with great power comes great responsibility. We need to consider the teams’ cognitive capacity as well as organization size.

3. By applying four fundamental topologies and three interaction modes from “Team Topologies”, we can describe different ways to split responsibility for our CI/CD system and decide which one best matches the organization and teams’ needs.

Manuel Pais is co-author of Team Topologies: organizing business and technology teams for fast flow. Recognized by TechBeacon as a DevOps thought leader, Manuel is an independent IT organizational consultant and trainer, focused on team interactions, delivery practices and accelerating flow.

  • Get the latest DevOps jobs, events and curated articles straight to your inbox, once a week

  • Community Partners