TDD Heuristics: One failing test at a time

When you are changing an interface or API that is widely used, it can be tempting to do the change in one go and break a lot of tests at once, assuming you can just fix them. You risk ending up chasing failing tests around for hours, with lack of good feedback why they fail. Furthermore, you risk breaking something along the way, because you have created holes in your safety net!

Team Fluency Feedback with Systems Thinking

To get better insights in how a team can grow and what support they need from their organization, we use the Agile Fluency® model and associated tools. In this post, we’ll share how we run an Agile Fluency team diagnostic workshop and how we use systems thinking techniques to arrive at recommendations for both the team and management.

Product Hurricane Maps to take into account tech debt when roadmapping

Recently we got asked: “How do we (as a development team or larger group) ‘sell’ technical debt to stakeholders?”

Christopher Alexander

Being alive
The search which we make for this quality, in our own lives, is the central search of any person, and the crux of any individual person’s story. It is the search for those moments and situations when we are most alive.
– The Timeless Way of Building, p. 41