Amy Phillips explains how the core principles can be used to drive process change and how their team removed many of the delays and frustrations from their release process.
Rachel Laycock focuses on the architecture of an application, addressing patterns such as microservices and evolutionary architecture, which can speed up delivery.
Rebecca Parsons explores the relationship between evolutionary architecture, continuous delivery and microservices, focusing on how they support each other in the creation of complex systems.
Jutta Eckstein presents techniques that helped her to create a common culture in different global projects she worked on.
Ken Kousen introduces Gradle to Android developers and shows how easy it is to integrate into Android projects.
Chad Fowler attempts to convince people that keeping things "tiny" –small iterations, small methods, small teams - is the best thing one can do for himself and his team.
Neil Mitchell introduces the Shake build system. Users of Shake write a Haskell program which makes heavy use of the Shake library, while still allowing the full power of Haskell to be used.
Daryl Chan, Martin Kearns present The Lens - a physical space orientated around dialogue, transparency and co-creation, discussing techniques used to stimulate inquiry, curiosity and introspection.
Andy Carmichael shares the experiences of a team new to Scrum adopting a customized Kanban process that would allow changes that were kept only if they were confident they resulted in improvements.
Brindusa Axon, David Evans debate the pros and cons of using stories and discuss practices and techniques for improving them.
Arnaud Pflieger, Baeli Dimitri present their practices and tools: Octopus-a git branching model, no dedicated testers, no ops, Selenium, Zeno – a diff tool comparing production and staging code.
James Grenning takes a look at why the technical practices of TDD, refactoring, continuous design, clean code and automated testing can help people and their organization be great.