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, and 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.
David Hussman advises on story mapping: pick an idea, choose someone that might be helped by that idea, build a story map as a way to explore that person’s experience, and start the customer journey.
Jim and Michele McCarthy discuss the Core Protocols that make a common platform for an organization’s culture design.
Terry Yin explains different programming exercises, outlining the difference in their effectiveness.
Bob Gower provides a holistic perspective on Agile: foundational concepts, the place of Agile practices and concepts, and the specific steps to improve product quality, morale, and time to market.
Bas Vodde explores five principles of managing software development resulting from his own development and coaching management experience in several large agile development projects.
Thushara Wijerwadena discusses aligning practices in various departments in an organization with those of an agile development team, addressing both the challenges and solutions to meet them.