Cédric Champeau demonstrates how Gradle inherits from good practices like what Maven offered, but goes beyond by generalizing the concept and allowing to define conventions.
Based on his experience at Uber, Matt Ranney explores why the build or buy tradeoff is so difficult, and makes some recommendations for both vendors and users.
Anders Ivarsson discusses how teams are autonomous at Spotify, how they are organized in squads, chapters, tribes and guilds, and how management and leadership works in their company.
Margaret Morgan discusses adopting an Agile mindset which is not only about IT delivery but also to maximize productivity, quality and responsiveness to changing markets and priorities.
Ben Linders talks about the why and how of Agile retrospectives, with many practical tips, stories, and examples.
Scott W. Ambler explores disciplined agile strategies to avoid and remove existing technical debt, how to fund the removal of technical debt, and related industry data.
Todd Charron argues that for success it is necessary to go beyond a change of processes and tools, to change how people in an organization see themselves and their role in it.
Erwin van der Koogh discusses the habits that seem to stand behind successful organizations, Agile or not: simplicity, trust, cross-functional, autonomy, open, mastery, and customer focus.
Hans Dockter discusses how to solve the challenges of standardization, dependency management, multi-language builds, and automatic build infrastructure provisioning.
Stuart Bargon discusses how to “descale” an organization, removing the extra weight and making it agile, showcasing the transformation of one of the oldest Australian public institutions.
Angela Ferguson explains why the physical environment is important to a successful Agile team and it can create both engagement and productivity among teams and individuals.
Michael Sahota how to produce organizational change by inviting it and not forcing it and by using the Laloux Culture Model.