Kolton Andrus is working as "chaos engineer" at Netflix which means he is getting paid for breaking things in production. We are talking with about how to improve overall system quality by injecting failures in production systems, about the idea of "anti-fragility" in the context of software and about how engineering teams of all layers can benefit from a failure injection infrastructure.
Steve Thair on introducing DevOps in large organizations, the particular challenges they face (from ROI based finance models to technical debt to improving communication) and how to address them.
Ruud Wijnands talks about things that can and do go wrong with Agile transitions, improving technical skills and practices, supporting people in learning, the value that agile can bring to organizations and giving managers more insight into the possibilities of agile, helping teams to increase their agility and what managers can do to increase the success of agile transitions.
Tim Ottinger talks about things that can and do go wrong with Agile transitions, why facilitation matters in agile, increasing the understanding of agile, what is needed to create trust in the organization, the importance of technical practices in Agile, improving technical skills and practices and the “Taking back Agile” initiative.
Three speakers from VersionOne discuss the importance of strong technical practices, software craftsmanship, how agile software development is similar to working in the theatre and how to get the right balance in documentation.
Elisabeth Hendrickson discusses her move from consulting to take on the role of Director of Quality Engineering for Pivotal Labs, how important engineering technical practices are to building quality in from the ground up and how scaling agile across many teams requires a structure that supports self-organization within organizational constraints.
Emma shares her view on Systems Thinking and why is it important in modern organizations that want to learn and move forward. She also delves into other topics from her experience such as working in the Middle East, women and technology and work-private life balance as a working mother.
Bryan Beecham (aka Billy Garnet) reminds us that "XP not dead!" and shares his approach to teaching TDD and refactoring with Lego and applying XP and craftsmanship in teams as well as the human body.
Crista Lopes discusses the idea of using constraints to define styles of programming and architecture. Also: large scale static analysis of open source code, Open Simulator and VR, and much more.
Neil Killick discusses his background in Agile and his thoughts on estimation in Agile software projects, in particular the discussion around #noestimates.
Gojko Adzic talks about the need to iterate and learn about business value before jumping into solutions. Impact Mapping helps visualize and learn which behavior changes impact business results. Those changes might not even require any kind of software delivery.