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.
Shane Hastie presents examples of how the most innocent of question or suggestion can send teams into a spin, and suggests a number of techniques to help create an environment where real communication can happen, irrespective if your team is co-located or distributed.
Jack Singleton discusses how to improve code readability and maintainability in Scala, and how to be productive with Options, Immutability, and the Collections library.
Seb Rose wonders if estimates are worthwhile and discusses what business people – Steve McConnell, Demarco, Lister, Disraeli - have to say about this.
Martin Thompson focuses on the evolution of Java and how it contrasts to C/C++, covering the cultural challenges of pushing the limits of performance and how to collaborate with industry experts and organize teams, which often stands at odds with the culture in many organisations.
Viktor Klang discusses approaches to writing software without building a complex, full of bugs and hard to maintain basecode.
Dan North believes Agile scales if teams achieve contextual consistency through shared guiding principles, a clear vision and a common understanding.
Ian Cooper reminds what was Kent's original proposition on TDD, what misunderstandings occurred along the way and suggests a better approach to TDD, one that supports development rather impeding it.
Jon Skeet provides practical advice on designing APIs using immutability, separation of concerns and other principles, resulting in elegant and reusable code.
Tim Lister presents the advantages—and the dangers—of practicing risk management in an adult-like fashion, offering a process for tailoring an organization and discussing how an organization can grow up.
Patrick Smacchia shares code analysis-related practices -structuring code, measuring code quality, automated tests, code contracts, reporting progress, trending- based on his experience with NDepend.
Martin L. Harbolt focuses on methods of providing data to a team to help them remain focused and maintain the rhythm necessary for success: KanBan boards, burn down charts and others, with examples.