Story points? Yeah, it might not be the best tool in the Agile toolbox

Home

News: Story points? Yeah, it might not be the best tool in the Agile toolbox

  1. If your managers are judging your productivity by the velocity of your development, and velocity is calculated as the number of story points completed over time, then what is the best way to improve your productivity without actually doing any more work? Simply make every stroke of the keyboard a completed story.

    In his article entitled Stop Using Story Points, Joshua Kerievsky talks about the problems you can get into when judging the productivity of a team by dividing story points by time.

    "One day in 2004 a team was asked to go faster. This team had an average velocity around 52 points per iteration. Their velocity would fluctuate by a few points, but generally remained steady. Yet just weeks being asked to go faster, the team's velocity jumped up into the high 80s.

    "I asked someone what happened. I was told 'these days around here if you sneeze, you get a story point.'"

     

    Read the full article: Stop Using Story Points

     

  2. As stated, story points are not there to judge productivity. What he observed is the same as could be observed with LOCs. What is reported is typical of people gaming a system. The boss is apparently pulling a Nigel.

    http://en.wikipedia.org/wiki/Up_to_eleven

     

  3. The dude abides[ Go to top ]

    I noticed that on Twitter, Agile Manifesto signer Jon Kern, noted that he avoided story points as well.

    Yeah, it's definitely people working the system. One must always be aware of the human condition.

  4. Again and again, metrics that can be used to assess productivity should be immune to conjectures from team members. That's common sense.

    http://caminao.wordpress.com/system-engineering/project-management/functional-size-measurements/

    http://caminao.wordpress.com/system-engineering/project-management/requirements-metrics/