Rachel Davies talks about the practical experience from teams using XP for 8 years, what they dropped and what elements of XP they adapted to have better infrastructure for global development.
Adam Yuret discusses how a focus on resource efficiency impedes flow while creating mountains of failure demand and fracturing an organization into competing silos.
Garrett Smith introduces Drunken Stumble, a development method in two stages: a lean, which represents the goal of the programmer or team, and a stumble, which is a series of automatic "next steps".
Cedric Mainguy introduces Serious Games, showing how it can help with training, hiring, generating new ideas, making meetings more effective, feature prioritization, vision sharing, strategy building.
Shane Hastie conducts a workshop addressing the role and skills needed in product ownership, and provides hands-on experience with some specific tools to assist with product ownership.
Peter Pilgrim presents the experience of adopting Scala in the digital enterprise. He provides technical and development advice to agile teams new to implementing Scala.
The panelists discuss topics related to Agile Software development within the same three different categories as the three tracks of the conference: Organization, Practices and Technology.
Mike Pearce tells the story of how MOO manages to keep a fresh, startup-like culture that fosters innovation and values collaboration, while still delivering products and looking after its staff.
John Sheehan presents choices – queues, proxies - helping a microservices architecture to stay robust and reliable, along with automation strategies allowing Runscope to deploy code 100 times a day.
Matt Barcomb discusses how leaders should evolve from "managing resources" to "designing systems", balancing authority with accountability and the issue of compensation plans based on performance.
Stefan Tilkov entertains the audience with architectural disasters in software projects, how excellent ideas turned into nightmares, how one can slowly but thoroughly introduce incredible complexity.
Steve Smith discusses why Release Testing is an anti-pattern, and offers an alternative risk reduction strategy.