Get the latest DevOps jobs, events and curated articles straight to your inbox, once a week
Source: London Continuous DeliveryJuly 2020 Meetup
Join us for an evening of great discussions & talks.
Zoom link will be shared on 14th July.
What's the plan?:
18:00 - Welcome and run through the agenda and tools we will use to facilitate the evening's event
18:15 Talk 1
18:45 Q&A with Allan
19:00 Talk 2
19:30 Q&A with Manuel
19:40 Open Space
20:00 Retro and Good Bye
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 allankelly.net/blog 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.
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.