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.
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.
Portia Tung discusses the concept of Hope, trying to help us better understand the relationship with Hope and figure out how to achieve even our most ambitious of goals.
Steve Smith discusses why Release Testing is an anti-pattern, and offers an alternative risk reduction strategy.
Kevlin Henney advises on writing Good Unit Tests (GUTs) by treating testing as a form of communication with multiple levels and forms of feedback.
Alberto Brandolini discusses how the Theory of Constraints, Kanban, CQRS, Domain-Driven Design, EventStorming and UX blend together to solve the real problems in software development.
Mike Bowler discusses CD, the build pipeline and version control practices and automated testing, exploring best practices and pitfalls, and making the deployment question a business decision.