Loading…
DevOps World | Jenkins World 2019 Lisbon has ended
Back To Schedule
Thursday, December 5 • 16:15 - 17:00
Why You Need to Think About Team Design for CI/CD

Log in to save this to your schedule, view media, leave feedback and see who's attending!

At Jenkins World 2018, Kohsuke Kawaguchi talked about the need to move away from Jenkinsteins, those single-headed monsters that eat all our food (resources) and steal our peace of mind.

Jenkins X, Pipelines as Code, Configuration as Code, Evergreen, and Serverless Jenkins are all important initiatives to achieve modern, fast and reliable software delivery. However… there’s still something we need to talk about and that is team organization for effective continuous integration/continuous delivery.

Should every application team own and maintain their own instances and flavors of Jenkins, since it’s all code now? Or do we still need a Jenkins admin team to handle Jenkins for everyone in the department/org so they only have to worry about their own pipelines and nothing else? Or something else, like a CI/CD platform providing out-of-the-box solutions that can be customized by application teams to fit their specific needs? The answer, as you probably guessed, is: it depends!

But just like we are advancing our tools to become easier to install, run and update, we also need to think about how to design our teams and responsibilities for transparency and ownership of both the CI/CD system (it’s actually a product) itself and the application pipelines.

This talk draws on research and case studies from the book Team Topologies by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.

Key takeaways:

1. Moving to fast, distributed, and reliable CI/CD systems is not just a matter of better tooling, 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 (which btw might change quickly).

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.

Speakers
avatar for Manuel Pais

Manuel Pais

Co-Author, "Team Topologies"
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 accel... Read More →



Thursday December 5, 2019 16:15 - 17:00 PST
Auditorium VII