(A talk given at PIPELINE Conference – March 2017 – Continuous Delivery At Scale – https://pipelineconf.info/2017-event/speakers/)
“Continuous Delivery is fairly easy to implement in a “two-pizza team”. But what about when you have to adopt the practice across 10s or 100s of teams with legacy infrastructure, governance and security concerns not to mention clashing cultural norms. Not so simple.
Continuous Delivery is not a tool or a single team practice. There are several factors to a successful implementation: organisational, process and architectural. Each one will require significant changes in your organisation. I’ll share with you the common pitfalls and anti-patterns in each of these areas, which will hinder your ability to deliver your features and products rapidly at scale.”
Rachel is Head of Technology for North America at ThoughtWorks, and is based in New York. She has over 12 years of experience and uses her deep technical expertise to coach teams in Agile and Continuous Delivery practices. She is a member of the Technical Advisory Board to the CTO, which regularly produces the ThoughtWorks Technology Radar.