QCon is a practitioner-driven conference designed for technical team leads, architects, and project managers who influence software innovation in their teams.

Vladimir Sneblic, Lead Consultant at ThoughtWorks

Vladimir Sneblic

Biography: Vladimir Sneblic

Vladimir is a lead consultant at ThoughtWorks, a global consultancy focused on revolutionising the IT industry and making a positive impact on the society.
Vlad's main passion is in helping people resolve issues and challenges. In his career, he has worked in most roles associated with an Agile project; he draws on the knowledge gained on these projects to help coach and guide delivery teams in technical and Agile best practices. More recently Vlad has focused on the Continuous Delivery space and the challenges people face in delivering the right solutions to the customers in a repeatable, low friction way.

Twitter: @vsneblic

Presentation: Getting buy-in for implementing CD

Track: Solution Track Thursday 2 / Time: Thursday 14:30 - 15:20 / Location: Westminster Suite

Oh, you've read the book, listened to a few talks on CD and are convinced that this is something your organisation should be paying more attention to. But the first challenge is, how do you convince other parts of the organisation and the senior management that they should invest time and money into this initiative.This talk focuses on identifying some of the main obstacles to CD adoption and discusses approaches to resolving them. We will take a look at issues within the delivery team, team's interaction with the business as well as getting the buy-in from senior stakeholders.

Training: Continuous Delivery - SOLD OUT

Track: Training / Time: Tuesday 09:00 - 16:00 / Location: Westminster Suite


Getting software released to users is often a painful, risky, and time-consuming process. This tutorial sets out the principles and technical practices that enable rapid, incremental delivery of high quality, valuable new functionality to users. Through automation of the build, deployment, and testing process, and improved collaboration between developers, testers and operations, delivery teams can get changes released in a matter of hours–sometimes even minutes–no matter what the size of a project or the complexity of its code base.

In this tutorial we take the unique approach of moving from release back through testing to development practices, analyzing at each stage how to improve collaboration and increase feedback so as to make the delivery process as fast and efficient as possible. At the heart of the tutorial is a pattern called the deployment pipeline, which involves the creation of a living system that models your organization's value stream for delivering software. We spend the first half of the tutorial introducing this pattern, and discussing how to incrementally automate the build, test and deployment process, culminating in continuous deployment.

In the second half of the tutorial, we introduce agile infrastructure, including the use of Puppet to automate the management of testing and production environments. We'll discuss automating data management, including migrations. Development practices that enable incremental development and delivery will be covered at length, including a discussion of why branching is inimical to continuous delivery, and how practices such as branch by abstraction and componentization provide superior alternatives that enable large and distributed teams to deliver incrementally.