Adam Yuret discusses how a focus on resource efficiency impedes flow while creating mountains of failure demand and fracturing an organization into competing silos.
Helen Walton and Pete Burden offer insight into how important culture is to a business and happiness, and the practical tools needed to make a vision become reality.
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.
Colin Gislason explores cross-culture similarities and differences on the African continent to find practical lessons in building technology.
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.
Ryan Behrman runs a workshop on how to be a more effective change agent, using "Change poker" in teams to experience various aspects of change and to share best practices.
Yan Cui discusses lessons learned, successes and challenges, and how a graph database enabled the Gamesys small team of game designers to stay agile and focused on delivering new content to players.
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.