I would point out that Martin Fowler, Kent Beck and Gergely Orosz were writing that you cannot measure productivity of a single team member. *You can get a rou

I would point out that Martin Fowler, Kent Beck and Gergely Orosz were writing that you cannot measure productivity of a single team member. *You can get a rough sense of a team's output by looking at how many features they deliver per iteration. It's a crude sense, but you can get a sense of whether a team's speeding up, or a rough sense if one team is more productive than another.* So in that sense "value add time" will be a valid metric. But it is still not a single number that one can give without context to the CEO, that CEO still has to ask questions like "we usually have X time spent on fixing bugs, aren't you gaming the system to get your bonus?". That is the CEO job to understand the metric not to be gamed...