Nicole Forsgren shares the results of studies spanning 4 years and 25,000 DevOps data points: continuous delivery and Lean management practices improves quality and security outcomes.
Steve Green discusses balancing emergent designs with intentional planning, common architecture principles, guidelines for measuring good architecture, and an evaluation of agile techniques.
Marina Cantacuzino presents lessons on reconciliation and forgiveness learned from real life cases, teaching how to overcome division, resolve tension and learn to embrace difference.
Tushar Dadlani focuses on lessons learned while building the continuous integration pipeline for deploying Pivotal Cloud Foundry to production.
Håkan Forss introduces Improvement Kata and Coaching Kata, as well as two core habits for transforming a Lean learning organization to improve a business.
Rob Scherer and Rob Alford discuss the Design Sprint process used by Google Ventures, some of the changes made to it and lessons learned along the way.
David Xia explains how Helios testing framework drives integration tests and spins up self-contained environments during test runs, increasing Spotify’s code quality and successful deployments.
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..
Perry Timms explains how leaders can create a learning strategy, culture, community and energy to power themselves and their people to a future of better understanding and ability.
Lisa Frazier discusses how to adapt as a leader in different contexts by leveraging Agile methods, sharing lessons learnt from rural and urban Australia and experiences from Silicon Valley start-ups.
Simon Raik-Allen explores how alternative Agile Manifesto style statements can be used for other challenges and specifically around the building of a technology platform.
Ryan McKergow discusses how others have implemented scaled retrospectives, what worked and what didn’t work for his company, sharing tips on how to run scaled retrospectives and avoid wasting time.