Tom Gilb keynotes on 10 key Agile principles: Control projects by quantified critical-few results, Give developers freedom, Estimate the impacts of your designs, Involve the stakeholders, etc.
Rachel Davies leads an interactive session with exercises on how to plan and facilitate an effective retrospective.
Baruch Sadogursky and Fred Simon discuss the Groovy version of the epic Java Puzzlers.
Robert Reppel considers that architects should build software-centric systems as a user experience for customers, products owners, developers, IT, testers and other participants.
Adam Tornhill teaches how to predict bugs, detect architectural decay and find the code that is most expensive to maintain, how to evaluate knowledge drain in a codebase, and much more.
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.
Vik Kheterpal discusses how to focus on individuals and how teams are formed for a common goal.
Ken Kousen introduces Gradle to Android developers and shows how easy it is to integrate into Android projects.
Cecile Diener shares her experience at eBay Europe building small self-managed teams along with their practices.
Rob Cromwell talks about the evolution of Inkling's culture, and the many lessons learned in building "conscious" teams that work well together in the pursuit of technical excellence.
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.