A recent Improving Professional Scrum Product Backlog Management class brought up the old warning about measuring activity by story points. It reminded me of a meeting years ago where a manager made an offer that still makes me shake my head.
The offer
I was on a team that was running what we called “Scrum”, though the quotes got heavier as the meeting went on. The managers wanted us to work harder and finish more work. Their idea of harder meant more stories, and their idea of more stories meant more story points. To make it interesting, they offered the team members money based on how many story points each person completed in the sprint.
The whole team looked at each other. Nobody said anything for a moment (the pause of disbelief). Then we rejected it unanimously. We were not going to do that. We were a team.
Why it broke the moment we heard it
The problem was obvious instantly. A sprint is not a sales contest. Story points help the team forecast and align; they are not a scoreboard. The minute you attach cash to them, the number becomes the goal. People start gaming estimates, rushing work, and hiding anything that does not translate cleanly into a higher point total.
Worse, it would have split the team. The person pairing with others, reviewing code, and helping teammates push their PBIs across the finish line might not have a single commit or story point to show for it. That contribution is invisible to a points-based scorecard, but it is what keeps a team moving.
The metrics we cannot see
That part stays with me. The source control graph does not show the two hours someone spent untangling a teammate’s problem. The sprint board does not show the quiet pairing session that prevented a bug. Story points definitely do not show that.
If you reward individual points, you teach the team that invisible help is worthless. You teach people to optimize for what gets measured instead of what needs to be done. The team knows the difference, and in our case, we said no before the idea even had a chance to take root.
What I took from it
That meeting shaped how I think about team dynamics and metrics. Compensation for story points sounds like a clever incentive, but it is a trap. It replaces trust with competition. It turns a shared goal into individual scorekeeping.
The class refreshed that memory and gave it a name. Product backlog management is about understanding the work, protecting the team, and keeping the focus on value that reaches real customers.
The best teams measure contribution by whether the work got done well, not by who gets credit for the points. That is harder to put on a spreadsheet, but that is where the real value is.
Leave a Reply