Jez Humble, TweetAuthor of "Continuous Delivery", Principal Consultant, ThoughtWorks
Biography: Jez Humble
Jez Humble is a Principal Consultant with ThoughtWorks, and 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: TweetDevOps Culture And Practices To Create Flow
Practitioners are often frustrated that they can’t their organizations to change their behaviors, despite executives proclaiming they want better, faster and more. Like dieting, changing individual and organizational behaviour is the most important, and yet also the most difficult thing to fix.
In this tutorial, Gene and Jez will show the techniques they have found effective in enabling organizations to have their “a-ha” moment - and then follow through. We’ll help you understand how to grow a DevOps culture, implement continuous delivery, and build products using lean startup principles.
We'll present patterns derived from Lean, Agile and Theory of Constraints that enable making cultural, process, and architectural changes incrementally, while transparently creating value that everyone will appreciate. We'll provide real-world examples from organizations that have made this change. We'll discuss how to deal with thorny issues such as governance and budgeting. And we'll show you the tools you can use straight away to start making things better.
This tutorial is aimed at practitioners who want to kick-start change in their organization. There’s no hands-on-keyboards, and we won’t spend much time discussing the toolchain, and the tutorial is suitable for developers, sysadmins, testers, managers, product owners and anybody else interested in concrete techniques to make things better.