These are chat archives for jdubray/sam

1st
Aug 2017
Jean-Jacques Dubray
@jdubray
Aug 01 2017 13:45
@antanas-arvasevicius as I mentioned, it has to be interpreted with care. In general people are shocked with the metric since it integrates every activity of the project, but at the same time, I feel it gives a reasonable picture of the "technology productivity" (not people productivity). Of course it should vary based on the type of project.
For me I view it as a metric that helps you target low hanging fruits that kill people productivity, and I make it very very clear that this is not about people, or even a race to code faster, it's about the big picture of a project, where you can get 30-50% improvement jut by tweaking a thing or two.
It's also a metric that can help managers get a sense that something is hampering the project's progress. I like it a lot better than user story-based velocity. The temptation is way too high to fudge that metric just to look good. That's a watermelon metric as we say in French, beautiful green on the outside, deep red on the inside.