James Grenning takes a look at why the technical practices of TDD, refactoring, continuous design, clean code and automated testing can help people and their organization be great.
Lynne Cazaly shares ways to achieve greater buy-in, clearer communication and higher levels of engagement with team members, stakeholders, sponsors and business units using "visual agility".
Kiro Harada attempts to clear up some misconceptions on several Lean practices: Value Stream and Flow, Visualization, Pull-System, 5 Times Whys, Kanban, Kaizen.
Joseph Yao introduces Transformation Priority Premise (TPP) as a way to learn TDD.
Bas Vodde introduces Large-Scale Scrum (LeSS), a framework for scaling Scrum to medium to large projects while staying true to the original Scrum principles.
Linda Rising discusses the “agile mindset” - an attitude that equates failure and problems with opportunities for learning –, sharing practical suggestions to become even more agile.
David Hussman combats the addiction to a specific process, discussing various topics such as product thinking, regression deficit, building teams and connecting programs to portfolios.
Mike Mallete discusses the why performance appraisals fail and what can be done instead.
Neil Killick exposes the risks inherent to the estimation culture, proposing practical alternatives for the project and spring level.
Kent Beck addresses several questions: Why are programmers so often ill at ease with themselves? What can we do to become comfortable in our own skins? What might happen as a consequence?
Karin Verloop discusses how to structure for innovation in a repeatable, practical and affordable way, addressing: the 3 levels of innovation, investing in innovation, a sustainable digital framework.
Kevlin Henney addresses the motivation, implications, pros and cons of a craftsmanship view of software development, as well as touching on other metaphors and their implied practices.