> Engineering productivity can’t be measured by tracking new features.
Garbage in, garbage out. And as a measure of engineering productivity, story points/feature count/Jira are pretty much garbage!*
Back in 2013 when I was doing consulting for Fortune 500s, even the "Agile practitioners" on our team got carried away abusing Jira and story points to do crazy cross-team comparisons and micromanagement. And these were exactly the people that were supposed to know better! That's what they being paid for, after all.
There are many things that should be purely internal measures within a team, yet anything quantified and easily accessible is always rife with misuse. Can't imagine how much worse that will be once AI makes even more of that surface area accessible, and worse yet can gamify its output to outperform on such measures.
* Story points can have value within a team, but that's a separate discussion
Back in 2017 I had people who had the full time job of Scrum Master. Oh have the times changed. Luckily my team doesn’t abuse Jira, but some companies… oh boy
Garbage in, garbage out. And as a measure of engineering productivity, story points/feature count/Jira are pretty much garbage!*
Back in 2013 when I was doing consulting for Fortune 500s, even the "Agile practitioners" on our team got carried away abusing Jira and story points to do crazy cross-team comparisons and micromanagement. And these were exactly the people that were supposed to know better! That's what they being paid for, after all.
There are many things that should be purely internal measures within a team, yet anything quantified and easily accessible is always rife with misuse. Can't imagine how much worse that will be once AI makes even more of that surface area accessible, and worse yet can gamify its output to outperform on such measures.
* Story points can have value within a team, but that's a separate discussion