Lynne Cazaly shares insight on how to start a high impact meeting or workshop, the process, the agenda, and the tools that can help facilitate such an event.
Elinor Slomba discusses sharing projects with other organizations using Agile principles and practices, highlighting Context, Collaboration & Connection through three case studies.
Ian Barber discusses the importance of behavior, domains and clarity of the names used when writing software or building systems.
Michael Seifert shares lessons learned working on various design projects and the process of changing the tools while doing it.
Francis Fish proposes a new agile manifesto that is influenced by Lean and the manufacturing movement.
Donald Belcham presents design patterns and development concepts that protects one’s code from external systems that may change in uncontrollable ways.
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.
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.