Conclusively demonstrating why you should listen to others…
“Should” we follow a plan or test hypotheses? I don’t see these as opposites, but I do see an underlying system that tends to result in a continuum. And there’s a missing third item. Let’s explore.
Along the way, we’ll discover a primary source of technical debt, of organizational mis-alignment, and what we can do to solve that root cause.
Continue reading “Plans vs Hypotheses”Another good question came over the wires at work. My reply grew too long and I figured more people would want to see it. Besides, this way I can blog and call it a legitimate business activity.
Problem statement: what patterns and strategies work for choosing when and what to refactor? Does this change at scale? Continue reading “Fixing Legacy: What Should I Blow Up First?”
While talking with people at Agile Roots last year, someone asked me how to measure technical debt. I came up with a metric that, while highly susceptible to gaming, can be really handy for a team to use internally. Continue reading “Quantifying Technical Debt”