Nick Beenham describes how the Enterprise Services Team at Comcast transformed from large monolithic deployments with cycle times of anything from 90 days to cycle times measured in hours.
Michael Venezia discusses creating a container-friendly environment starting with CI/CD of container images, providing a roadmap to meet an organization's needs and fostering cooperation.
Nicole Forsgren shares the results of studies spanning four years and 25,000 DevOps data points: continuous delivery and Lean management practices improves quality and security outcomes.
Tushar Dadlani focuses on lessons learned while building the continuous integration pipeline for deploying Pivotal Cloud Foundry to production.
Peter Mounce discusses CD at JUST EAT, covering package contracts, feature toggling, team sizes and responsibility, AWS AutoScaling, ELB, CloudFormation, build scripts for server images, etc..
Susan Potter describes a toolchain and principles for defining infrastructure in code, versioned with the code, providing repeatable configuration, ephemeral testing and consistent CI/CD environments.
Dave Farley discusses using acceptance testing to work quickly and effectively, building functional coverage for complex enterprise-scale systems, and managing and maintaining those tests.
Sam Adams talks about testing at LMAX Exchange, extending functional tests into live monitoring of production through isolation, and moving fast through incremental delivery, quality and automation.
Sangeeta Narayanan looks at the role of containers in simplifying and increasing the reliability of the process of releasing and operating the Netflix software.
David Alpert shares 10 tips on streamlining the delivery pipeline to make the process fast and smooth.
Steve Smith compares and contrasts different types of Feature Branching and Trunk Based Development, and explains why Continuous Delivery without Continuous Integration is not working.
Mark Lines keynotes on the Disciplined Agile Delivery (DAD) framework, scaling an Agile strategy, and practices for successfully scaling Agile.