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.
Katherine Kirk shares real life, practical steps and techniques that she's successfully used to help solve tough tech people issues with teams, executives and divisions.
Chris Young, who runs a live software system, discusses using Kanban metrics and practices with tools like Graphite and Grafana, and shows how the feedback helps businesses to make informed decisions.
Dan North discusses a number of feedback models and techniques, where and how to apply them, explaining the sandwich feedback model, how it works and why it usually doesn’t.
Agustin Villena, and Manuel Cepeda discuss using Lean principles and Kanban tools to empower the Chilean government teams to embrace uncertainty and achieve/surpass defined objectives.
We're all aware that the industry is moving from Object-Orientation toward Functional Programming, but the move may be even deeper than that.
Justin Cormack talks about the Docker unikernels build, ship and run pipelines and how the changes they are seeing lead to unikernels in production.
Manuel Vacelet and Pascal Rapicault introduce Tuleap - Scrum, Kanban, and generic bug tracking –, explaining how to integrate it with the Eclipse toolset and Bugzilla.
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.
Shen Yang discusses how Rally Software scales Agile through "Big Room Planning" which helps surface all problems and dependencies and enables decisions to be made and actions to be taken in real time.
Jim Benson discusses why Kanban is helpful: enables clarity of purpose, promotes shared understanding, recognizes individual input, depersonalizes work, respects problem solving, and others.