Over the years, I've wondered why experienced software teams struggle to improve. Why do smart teams keep revisiting the same issues in retros without real progress? Not the "writing better code" variety of issues. The answer, more often than not, is that they're missing three things at once: real data, an explanation of what's driving the data, and a way actually to change it. Usually, you get one, maybe two. Never all three. I have been a consultant/CTO/lead architect for about 30 years. My...
No comments yet. Log in to reply on the Fediverse. Comments will appear here.