Geoff Bones, Luke Drury share the lessons learned setting up code kata programs in several companies, what has worked and hasn’t.
Thomas Epping considers that case studies, even successful ones, should not be blindly applied everywhere, but one should take only what’s useful for one’s circumstance.
Ben Ross considers that physical environments affects agile practices, exemplifying with MYOB’s transformation of a shopping center’s roof into the largest open space in Melbourne.
Sandy Mamoli explains how Trade Me is using Portfolio Kanban to reduce WIP by prioritizing projects, focusing on the important ones rather than urgent ones.
Lisette Sutherland, Elinor Slomba share stories of successful remote distributed teams, how they built relationships and trust, and how they raised the quality of their communication.
Michael Bryzek shares lessons learned from startup to a leading ecommerce companies, starting with behavioral psychology and reflecting on the decisions made and tradeoffs considered as they scaled.
Jeff French shares from his experience how to convince organizations to implement Agile methodologies.
Martin Thompson discusses the major steps in the evolution of Java and how it contrasts to alternative technologies, and the challenges of pushing the limits of performance.
Darren Hobbs shares lessons learned building polyglot systems, the technology choices made. mitigating risk and delivering value.
Katherine Kirk reflects through case study examples on what continuous improvement feels like on the ground and explores how it can be better by learning from other industries, research and real-life.
Daniel Schauenberg provides insights into how Etsy develops software and what tools and processes they utilize to help them achieve their goals.
Dan North shares insight on how high-performing teams work, the patterns and ideas being genuine experiences from practitioners. This is Agile in actuality. Agile is an attitude, not a rule book.