Mike Breeze and Ma Qiang share the story of a distributed team and its Agile transformation, placing individuals and interactions over processes and tools and avoiding the dark side of Agile.
Anna Obukhova discusses the relationship between willpower and Agile practices sharing 10 tips that can lead to increased productivity.
Adam Krieger discusses improving CD: using feedback to improve customer satisfaction, treating DevOps as a responsibility, discovering the mindset and toolset necessary to deliver successfully.
James Ross discusses what concept maps are, how to construct one, what to do and what to avoid when creating one, and how to help a team build a shared mental model depicted in a concept map.
Doug Talbot explains the importance of measuring to the Lean feedback cycle providing advice on what to measure and how often.
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.