In this episode, Dave Farley shares his "10 Rules of Continuous Integration" – rules for organizing a team to implement this critically important aspect of modern software development. Dave practiced a version of CI back in the early 1990s, but refined his approach at ThoughtWorks in the early 2000s and is now considered an expert in the field.

Continuous integration is more than just build automation, it also requires a change in the way software development teams organize their work and, when implemented well, leads to a more disciplined approach to software development.

This disciplined approach is even more important when practiced as part of a Continuous Delivery Deployment Pipeline (CICD). Before Kent Beck introduced CI projects, they simply failed because teams couldn't merge their work. This is no small change, and continuous integration is a cornerstone of any effective CD approach.

———————————————————————————————–

If you want to gain Continuous Delivery and DevOps skills, check out Dave Farley's courses:
️ https://bit.ly/DFTraining

BOOKS:

Dave's NEW BOOK /"Modern Software Engineering/" is now available on
Amazon ️ https://amzn.to/3DwdwT3
In this book, Dave brings together his ideas and proven techniques to describe a lasting, coherent, and fundamental approach to effective software development for programmers, managers, and technical leaders of all experience levels.

/"Continuous Delivery Pipelines/" by Dave Farley
Paperback ️ https://amzn.to/3gIULlA
E-book version ️ https://leanpub.com/cd-pipelines

The award-winning original book “Continuous Delivery” by Dave Farley and Jez Humble
️ https://amzn.to/2WxRYmx

/"Accelerate, The Science of Lean Software and DevOps/

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.