Jez Humble, TweetCo-author of "Continuous Delivery", Principal Consultant, ThoughtWorks
Biography: Jez Humble
Jez Humble is a Principal Consultant with ThoughtWorks, and co-author of Continuous Delivery, published in Martin Fowler's Signature Series (Addison Wesley, 2010). He got into IT in 2000, just in time for the dot-com bust. Since then he has worked as a developer, system administrator, trainer, consultant, manager, and speaker. He has worked with a variety of platforms and technologies, consulting for non-profits, telecoms, financial services, and online retail companies.
Since 2004 he has worked for ThoughtWorks and ThoughtWorks Studios in Beijing, Bangalore, London, and San Francisco. His focus is on helping organisations deliver valuable, high-quality software frequently and reliably through implementing effective engineering practices in the field of Agile delivery. He also serves as Product Manager for Go, ThoughtWorks Studios agile release management platform. He holds a BA in Physics and Philosophy from Oxford University and an MMus in Ethnomusicology from the School of Oriental and African Studies, University of London.
Personal blog: http://jezhumble.net/
Book: Continuous Delivery (Addison Wesley, 2010)
Company website: http://studios.thoughtworks.com
Presentation: TweetScaling Devops
In this talk, Jez discusses how devops can be implemented in large organizations. He will provide a selection of the common issues with devops adoption, such as managing risk, compliance with regulation and frameworks such as ITIL, and meeting auditing requirements. He will show that devops in fact improves the ability of organizations to meet the goals of good governance. He will also provide examples of how devops has been implemented in organizations such as Amazon, through moving from projects to products and providing infrastructure as a service, and the benefits this provides.
Keywords: devops, itil, governance, risk management, compliance, infrastructure as a service
Target audience: managers, systems administrators, anyone interested in devops
Training: Continuous Delivery Tweet
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.
Inthis tutorial we take the unique approach of moving from release back through testing to development practices, analyzing at each stage how toimprove collaboration and increase feedback so as to make the delivery process as fast and efficient as possible. There will be interactive exercises where the audience practices using these techniques for themselves. At the heart of the tutorial is a pattern called the deployment pipeline, which involves the creation of a living system thatmodels 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 halfof 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 alternativesthat enable large and distributed teams to deliver incrementally.