We are delighted to announce that our keynote speaker Dave Farley will be accompanied by 6 other speakers, in 2 tracks focussed upon Culture, Process, Tools and Experience Reports.
Speaker Selection Process
The PIPELINE 2014 speakers were chosen via the following anonymisation process:
- Anthony received all proposals and acted as main contact point for questions, queries or anything else related to proposals.
- Anything identifying the speaker – name, email address, gender, race, nationality, experience, organisation – were removed from the proposal by Anthony according to this list
- Anonymised proposals were reviewed by the remaining PIPELINE team (2 male, 3 female)
A detailed account of the process is available in the blog post “Where are the female speakers? Here’s what we tried.”
We are grateful for the large number of high-quality submissions we received, and thanks to our anonymisation process we are confident our speakers have been selected entirely upon merit.
|Dave Farley – @davefarley77 – Blog|
|Many people working in software development spend their careers without seeing what good looks like. Our history is littered with inefficient processes creating poor quality output, too late to capitalise on the expected business value. How have we got to this state? How do we get past it? What does good really look like?
Dave Farley is co-author of the Jolt award winning book Continuous Delivery. He has been having fun with computers for over 30 years. Over that period he has worked on most types of software. He has a wide range of experience leading the development of complex software in teams, large and small. Dave was an early adopter of agile development techniques, employing iterative development, continuous integration and significant levels of automated testing on commercial projects from the early 1990s. More recently Dave has worked in the field of low latency computing developing high performance software for the finance industry.
Culture, Process, Tools
|Phil Wills – @philwills – Blog|
|In 2013, the Guardian deployed more than 10,000 times to it’s production systems, an order of magnitude more than previous years. This talk aims to convince you that very frequent production deployments are desirable and explain how a combination of cultural and technical changes can enable it.
Phil is senior software architect at the Guardian. He has worked on just about every part of the Guardian’s site and the tools which support it; building features, optimising performance and increasing resilience. Over the past two years, he’s helped the Guardian achieve *much* more frequent delivery.
|Allan Kelly – @allankellynet – Blog|
|Given that we know that iterative software development can work much better than ‘big bang’ or waterfall, should we apply the same process to organisational change? How about a backlog + iterations for shifting to a team structure which takes Conway’s Law into account, so that the organisation has a better chance of delivering the software systems it needs?
Allan Kelly is a software business consultant based in London. He has a strong interest and experience in the organisational aspects of software development, and is the author of Business Patterns for Software Developers, Changing Software Development, and Xanpan.
|Pini Reznik – @pini42 – Blog|
|This talk will explain how Docker and other containers (OS level virtualisation) can help to shorten the software development feedback loop by drastically reducing the overhead involved in deploying new software environments. This will lead to faster build and test execution and significantly simplify standardisation of development and production environments, to allow easier transition to Continuous Delivery.
Pini is a Configuration Management consultant at Ugly Duckling in Amsterdam, Netherlands. He has more than 15 years of experience in Software Development, Configuration Management and IT Operations.
|Adriaan de Jonge – @adriaandejonge – Blog|
|My client asked to help with their problematic two months release cycle. They considered lowering the frequency to a three months cycle. We proposed the opposite: increase the frequency of the release cycle using best practices from Continuous Delivery. Our proposal was accepted: we started the transformation of a full IT department towards Continuous Delivery. In this presentation I share our experiences proposing and starting up this project: what worked for us, what did not work and how we plan to approach the rest of the project.
Adriaan de Jonge is Principal Consultant at Xebia in The Netherlands. Adriaan specializes in Lean and Continuous Delivery. He is co-author of The Manager’s Guide to Continuous Delivery. Before this book, he wrote two developer’s guides on web technology, published by Addison-Wesley in 2011 and 2012.
|Alex Wilson – @pr0bablyfine – Blog
Benji Weber – @benjiweber – Blog
|At Unruly, an idea conceived in the morning can be making money by lunchtime. We will explain the culture, processes, and tools that help us achieve this. In particular, we will look at how we have maintained and adapted these facets of development during a growth phase, and problems we have run into along the way.|
|Tomas Riha – @TomasRihaSE – Blog|
|This talk focuses on the people side of Continuous Delivery and how the traditional roles of developer, tester, project manager and product owner are affected by Continuous Delivery. We had no idea that a Continuous Delivery implementation was a change project that focuses on changing the behaviour of the individuals. By treating it simply as a technical project we failed in all possible ways. This talk is a lessons learned talk focussed on people, not technology.
Tomas Riha is the technical lead on Volvo Group Telematics/WirelessCar’s framework team and as such he leads the development of their Continuous Delivery process and the supporting tools. The process has gone from a skunkworks implementation used by five to the centerpiece of a corporate wide new delivery strategy in about three years.
Note: the previously-announced talk by Christopher Marsh will not take place, and has been replaced by the talk from Allan Kelly.