Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
In the world of software development, tales and metaphors often serve as powerful tools to communicate complex ideas. One such tale is the Brothers Grimm’s “Seven at One Blow,” the story of a humble tailor whose feat is grossly misunderstood—and whose legend is inflated through a simple misunderstanding. Surprisingly, this story mirrors a common pitfall in Agile teams: the misuse of story point estimation, especially when teams or leaders start comparing velocity across different teams or use metrics out of context. In this blog post, we’ll explore the enduring lessons from the tale and how it relates to Agile estimation, the dangers of misunderstanding metrics, and how some may even game the system to appear more successful than they really are.
Have you ever witnessed or experienced the misuse of story points in your organization? How did it impact team morale and performance?
What steps can leaders take to ensure Agile metrics are interpreted and used correctly rather than as tools for comparison?
How can teams foster honest communication about their work without fear that their metrics will be misunderstood or misused?
Blog post: Seven at One Blow: Lessons for Agile Teams and the Pitfalls of Story Points Misunderstanding
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Yes, and in my experience the problem was rarely story points themselves. It was what the organization expected people to do with them.
Once velocity starts influencing comparisons, reporting or performance conversations, it gradually stops being a planning aid and starts becoming a target. Honest estimation then becomes harder, not because teams suddenly change, but because the system changes the incentives around the metric.
For me, one of the most useful questions is not "Are we measuring the right thing?", but "What decisions is this metric intended to improve?" If the answer is unclear, the metric is likely to create more noise than insight.
Psychological safety certainly matters, but so does governance. Teams are far more likely to estimate honestly when they know the metric will support better decisions rather than better rankings.
...
1 reply by Stelian ROMAN
Sep 13, 2026 6:28 PM
Stelian ROMAN
...
"The problem was rarely the story points themselves. It was what the organization expected people to do with them." I agree. I want to add that story points are a team metric, and organisations should not use them outside the team
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
Yes. I've seen story points used to compare teams and even evaluate individual performance, which was never their purpose. It usually led to defensive estimating and less trust in the metrics. Story points work best as a planning tool for the team, not as a performance measure. Clear communication about what these metrics are, and aren't, for goes a long way in preventing their misuse.
...
1 reply by Stelian ROMAN
Sep 13, 2026 6:32 PM
Stelian ROMAN
...
"Yes. I've seen story points used to compare teams and even evaluate individual performance, which was never their purpose." In my experience, most of the time, the problem starts with a wrong Agile adoption, with a trainer/consultant/coach/manager who is pushing story points as a replacement for traditional metrics like cost and time. Story points don't measure value to the organisation or to the customer.
Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Jul 08, 2026 3:59 AM
Replying to Luis Branco
...
Yes, and in my experience the problem was rarely story points themselves. It was what the organization expected people to do with them.
Once velocity starts influencing comparisons, reporting or performance conversations, it gradually stops being a planning aid and starts becoming a target. Honest estimation then becomes harder, not because teams suddenly change, but because the system changes the incentives around the metric.
For me, one of the most useful questions is not "Are we measuring the right thing?", but "What decisions is this metric intended to improve?" If the answer is unclear, the metric is likely to create more noise than insight.
Psychological safety certainly matters, but so does governance. Teams are far more likely to estimate honestly when they know the metric will support better decisions rather than better rankings.
"The problem was rarely the story points themselves. It was what the organization expected people to do with them." I agree. I want to add that story points are a team metric, and organisations should not use them outside the team Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
"
Saving Changes...
Stelian ROMANProject Manager| MicroSafetyCarlingford, New South Wales, Australia
Jul 09, 2026 9:17 PM
Replying to Lissette Indhira Pimentel Sosa
...
Yes. I've seen story points used to compare teams and even evaluate individual performance, which was never their purpose. It usually led to defensive estimating and less trust in the metrics. Story points work best as a planning tool for the team, not as a performance measure. Clear communication about what these metrics are, and aren't, for goes a long way in preventing their misuse.
"Yes. I've seen story points used to compare teams and even evaluate individual performance, which was never their purpose." In my experience, most of the time, the problem starts with a wrong Agile adoption, with a trainer/consultant/coach/manager who is pushing story points as a replacement for traditional metrics like cost and time. Story points don't measure value to the organisation or to the customer. Saving Changes...
Community Champion
