We are delighted to announce our keynote speakers for PIPELINE 2015!
|Linda Rising – @RisingLinda – Website|
|You have great ideas. You’re smart. The people in your organization are smart. Post Hoc, Ergo Propter Hoc — the rest is easy — simply make a transition plan and transparently explain the benefits. These and other organizational change myths will be tackled by Linda’s talk about patterns for introducing new ideas. She will provide some useful tips for helping you start on Monday morning to grow, step by step, any innovation.
Linda Rising has a Ph.D. from Arizona State University in the field of object-based design metrics and a background that includes university teaching and industry work in telecommunications, avionics, and strategic weapons systems. An internationally known presenter on topics related to patterns, retrospectives, agile development approaches, and the change process, Linda is the author of numerous articles and books: Design Patterns in Communications Software (SIGS Reference Library), The Pattern Almanac 2000, The Patterns Handbook: Techniques, Strategies, and Applications (SIGS Reference Library), and Fearless Change: Patterns for Introducing New Ideas. Her new book More Fearless Change: Strategies for Making Your Ideas Happen is now available.
|James Betteley – @jamesbetteley – Website|
|Is Continuous Delivery really an option for a team running VB6 and SQL 2000 on a Windows 2003 server? The principles of Continuous Delivery apply no matter how “legacy” your system is, but technical debt can be a formidable mountain to climb. This is a painful experience report.
James Betteley brings real business value through great Development & Operations processes, whether that be by using tools or implementing a new process or culture.
|Meri Williams – @geek_manager – Website|
|Bringing change to legacy systems and monolithic waterfall programs is daunting, but doable. In this session we’ll look at a real world example of how we undertook the technical, cultural and process challenges to move to continuous delivery in a big organisation. You’ll hear about the epic battles with the dreaded CAB (Change Approval Board), the fight to move architecture discussions from Word documents to the whiteboards, and the myriad smaller skirmishes along the path to delivering features to our users faster, safer & more measurably.
Meri is a geek, a manager, and a manager of geeks. She’s a CTO and also manages her own micro-consultancy ChromeRose which helps digital & technical teams be brilliant. Previously she led the Delivery Team at the Government Digital Service and worked in Procter & Gamble’s Global Business Services organisation for 10 years, starting out as a Developer, moving on to Product Management, and finally Programme & Engineering/Operations Management. She’s led teams ranging in size from 30 to 300, mostly with folks spread across the world.
|Dave Farley – @davefarley77 – Website|
|Writing and maintaining complex, production-like, acceptance tests is complex. In this talk I will describe approaches to acceptance testing that allow teams to: work quickly and effectively; build excellent functional coverage for complex enterprise-scale systems; manage and maintain those tests in the face of change and evolution in both the codebase and the understanding of the business problem. How do you fail fast? How do you make your testing scalable? How do you isolate test cases from one-another? How do you maintain a working body of tests when you radically change the interface to your system?”
Dave Farley is the co-author of the Jolt-award winning book ‘Continuous Delivery’ a regular conference speaker and blogger and a contributor to the Reactive Manifesto. Dave is an independent software developer and consultant, and founder and director of Continuous Delivery Ltd.
|Alex Wilson – @pr0bablyfine – Website
Benji Weber – @benjiweber – Website
|Testing in production used to be taboo – a sign that you had a lax attitude to QA. Now it is increasingly accepted that the opposite is true, and that if you only test your system in artificial environments you don’t really know it works. We’ll see some examples of the benefits we have experienced from testing in production – not limiting ourselves to just using live data, we deliberately avoid test environments and deploy changes straight to live – the only real source of truth about our application’s behaviour. We’ll also show you the tools and techniques we use to test feature functionality, performance, and failure scenarios in production ranging from increasing the throughput of our systems as a live load-test to deliberately introducing malfunctioning and badly behaved software as error simulations.
Alex Wilson has been a software developer at Unruly for approaching 3 years, during which time he has had the opportunity to experience and conquer different scaling issues. He takes particular joy in both the application of Continuous Delivery principles, and pushing the boundaries of XP through testing in production and mob programming.
Benji Weber is a full-stack developer at Unruly, where he leads an extreme programming team building a programmatic advertising platform using Java, and a sprinkling of other languages. Benji is enthusiastic about anything that helps build valuable and reliable software fast, including domain driven design, continuous deployment, and infrastructure automation.
|Keeping up with a team of developers who release every day is a tough job, but someone’s got to do it! Gone are the long, relaxing days of manual testing for weeks on end. Here is how we are keeping the acceptance testing process at JUST EAT as lean as possible.
Beccy has been working in agile testing for 7 years, for companies including ThoughtWorks and the BBC. She is currently working as a Technical Lead at JUST EAT, where she leads a team of Test Automation Engineers across Web, iOS and Android.
|Matthew Macdonald-Wallace – @ProfFalken – Website – Website|
|Continuous Delivery for Systems Administrators is a relatively new field, but they’re catching up with the Developers fast! In this talk I shares my experience on automated build and testing for systems administrators. I’ll take a look at how servers can be subjected to the same rigorous testing processes as software, using the same tool chains and even performing full integration tests of systems configuration and software using open-source, industry standard tooling.
Matthew is a DevOps Engineer at DevOpsGuys, spending most of his days on the command line helping customers deploy and maintain their code, whilst taking a “Test-Driven” approach to systems maintenance. In the past, Matthew has worked as a Python developer on the OpenStack project, managed a large-scale webhosting cluster and worked in a variety of other industries, all of which have shaped the way he approaches problems.
|The concept of Continuous Delivery and many releases a day is not something the average security team can accept easily. At our company we like a challenge. This talk shows how pipelines and automation tooling can significantly improve your security posture. Learn how to explain the security issues to security management and how to deliver measurable benefits – even in environments where security is a primary requirement. The Head of Risk & Assurance, and the Senior Manager for Monitoring and Response, will walk you through the journey of implementing Security automation in Continuous Delivery and its challenges.
Francois is presently the Senior Manager of Monitoring and Response for Betfair. He is responsible for overall Incident Response and Vulnerability Management Services. He is also actively involved in security automation projects supporting continuous delivery.
|Badrinath Janakiraman – @badrij
Akshay Karle – @akshay_karle – Website
|All too often we hear teams talk about Continuous Delivery as a destination. There are questions asked along the lines of what are the things a team needs to do in order to qualify as doing Continuous Delivery. We believe this is a flawed line of questioning. Continuous Delivery is not a destination that is arrived at by doing a fixed set of steps. We posit that Continuous Delivery is an axiom adopted by teams that informs their choice of architectural principles, the space of available designs, the selection of development practices, the choice of tools and most importantly, the culture of collaboration that they embrace. Thought of in this way, we believe Continuous Delivery can have as much of an impact on our software delivery process as testability and TDD have on our development processes.
Badri is a developer with ThoughtWorks Studios. For over 13 years, he has worked with ThoughtWorks as a consultant/coach with various clients and then as a developer/tech-lead on the Mingle team. Over the past couple of years he has been working as the Product Manager of Snap, a hosted Continuous Delivery tool that seeks to lower the barrier to entry to CD.
Akshay Karle is a application developer at ThoughtWorks. He has been working on Snap CI for almost a year and has keen interest in Linux, Continuous Integration and Ruby.