GOTO is a vendor independent international software development conference with more that 90 top speaker and 1300 attendees. The conference cover topics such as .Net, Java, Open Source, Agile, Architecture and Design, Web, Cloud, New Languages and Processes

Jez Humble, Author of "Continuous Delivery", Principal Consultant, ThoughtWorks

Jez Humble

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.

Twitter: @jezhumble
Personal blog: http://jezhumble.net/
Github: http://github.com/jezhumble/javasysmon
Book: Continuous Delivery (Addison Wesley, 2010)
Company website: http://studios.thoughtworks.com

Presentation: A Retake on the Agile Manifesto Part I

Track: People & Process - Day 1 / Time: Monday 14:40 - 15:30 / Location: Store Sal

The Agile Manifesto was the spark that brought about a shift in how software was being developed and as a result a wave of new Agile Methodologies such as SCRUM, XP, and Continuous Delivery have been introduced as  “better ways of developing software”.  Many development organizations have adopted these agile methodologies to improve their communication, increase customer involvement, and create happier and more efficient software teams.  

Fast forward to today, 13 years later, a discussion has emerged on what has happened since the Agile Manifesto was first published.  Prag Dave Thomas, one of the original 17 authors,  has written a blog post which has been heavily discussed online and on twitter titled "Agile is Dead (Long Live Agility) where he points out that the term "Agile" has become a marketing buzzword for companies and consultants to use as a way to commercialize the ideas behind Agile Software Development.  He also goes on to suggest that developers should program with “agility” rather then hoping solutions that are simply "coined" as  "Agile" will be able to solve some of the difficult problems that they encounter when developing software.

At GOTO, we think it is time to take a closer look at what has happened in the last 13 years since the Agile Manifesto was published and evaluate where the development community is going in the future.

Presentation: A Retake on the Agile Manifesto Part II

Track: People & Process - Day 1 / Time: Monday 15:50 - 16:40 / Location: Store Sal

The Agile Manifesto was the spark that brought about a shift in how software was being developed and as a result a wave of new Agile Methodologies such as SCRUM, XP, and Continuous Delivery have been introduced as  “better ways of developing software”.  Many development organizations have adopted these agile methodologies to improve their communication, increase customer involvement, and create happier and more efficient software teams.  

Fast forward to today, 13 years later, a discussion has emerged on what has happened since the Agile Manifesto was first published.  Prag Dave Thomas, one of the original 17 authors,  has written a blog post which has been heavily discussed online and on twitter titled "Agile is Dead (Long Live Agility) where he points out that the term "Agile" has become a marketing buzzword for companies and consultants to use as a way to commercialize the ideas behind Agile Software Development.  He also goes on to suggest that developers should program with “agility” rather then hoping solutions that are simply "coined" as  "Agile" will be able to solve some of the difficult problems that they encounter when developing software.

At GOTO, we think it is time to take a closer look at what has happened in the last 13 years since the Agile Manifesto was published and evaluate where the development community is going in the future.

Presentation: Lean Enterprise - Part I

Track: People & Process - Day 2 / Time: Tuesday 14:40 - 15:30 / Location: Store Sal

Large organizations often struggle to leverage software to create innovative products. This is due to a number of organizational factors, including culture, governance and financial management, and the application of portfolio and program management strategies that do not take advantage of the unique characteristics of software. This talk discusses how to take a lean approach to developing new products and running large scale programs of work, and how to grow a culture that enables organizations to turn software into a competitive advantage.

Presentation: Lean Enterprise - Part II

Track: People & Process - Day 2 / Time: Tuesday 15:50 - 16:40 / Location: Store Sal

Large organizations often struggle to leverage software to create innovative products. This is due to a number of organizational factors, including culture, governance and financial management, and the application of portfolio and program management strategies that do not take advantage of the unique characteristics of software. This talk discusses how to take a lean approach to developing new products and running large scale programs of work, and how to grow a culture that enables organizations to turn software into a competitive advantage.

Workshop: Continuous Delivery

Track: Training / Time: Wednesday 09:00 - 16:00 / Location: UNI 2

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.