Klaas, a technology advisor, argues that engineering is treated as a black box where companies invest resources but can't see how that translates to products. Story points and velocity only show input-output correlation, not cause and effect. He proposes measuring engineering through four pillars: operational needs, delivery, financials, and team health.
Chapters
Engineering is often seen as a black box. A lot of resources go in, and on the other side, you hope you get a good product out. We typically focus on things like story points or velocity or any number of ways that you measure activity. The problem with all those measures, you're really not measuring anything that shows you cause and effect. You're simply measuring an input and an output and hope there's a correlation. Think about it. If engineering really was a function purely of headcount, We'd all just be in an arms race to hire the most engineers we could. So it's clear that you're missing something there. Typically in leadership teams, there is a bit of a mismatch between the language used by engineering and language used by commercial people. And the fact that we have these 2 pillars almost hints at the problem right away. Engineering performance rests on 4 pillars. There is your operational needs, there's your delivery, there is your financial pillar, and lastly, there's a pillar around your team. Because I can guarantee you, with the right data, you do not need to be a technology expert to understand those decisions. I'm Klaas. I'm a technology advisor at Revalisco. I bring the right data that helps you separate signal from noise and make it digestible without needing to be a technology expert. Are you measuring your engineering organization in a way that clearly shows how technology investment drives business outcomes, or are you accepting it's a black box?