(Talk given at PIPELINE Conference 2016, London https://pipelineconf.info/2016-event/speakers/)

In large organisations, sometimes projects and parts of the code base get shuffled around between teams. Projects that have tons of responsibilities, that are business critical and that are hard to look after. What happens when a self-organised team that has a continuous delivery system in place receives one of these legacy product that is the antithesis of best practices? The talk approaches this issue with a real life example, highlighting the problems encountered and the solutions suggested and applied to each of them.

Gustavo Elias studied Computer Science in Spain. He started working as a C# developer during his last semester, and continued during so for a few more months. He quickly moved into IT training for a couple of years, teaching people how to use the company’s tools and its APIs. He moved to London in 2010 where he began his career in Java, first in the mobile billing industry and then in finance. He started learning about Agile and Continuous Delivery during his first job here, and has always been a practitioner and a fan. He has been a developer, a consultant, a team lead, and a tech lead during that time. He is currently working as a Senior Developer for IG Index in the Marketing Intelligence team, trying to make sense of Hadoop, Spark and other Big Data technologies.