Loading ...
Sorry, an error occurred while loading the content.

56951RE: [scrumdevelopment] User stories and relative complexity

Expand Messages
  • Jesse Houwing
    Jun 17, 2013
      Though there is some truth in the story, however flawed... Still, doesn't solve my problem 😉... Does highlight another one of the issues.

      Sent from my Windows Phone

      From: Charles Bradley - Professional Scrum Trainer and Coach
      Sent: ‎17-‎6-‎2013 20:50
      To: scrumdevelopment@yahoogroups.com
      Subject: Re: [scrumdevelopment] User stories and relative complexity

      > Here's something you may have not been looking for.

      I wouldn't bother reading this article.

      There's one major flaw in it.  The team goes from using story points to "counting stories" because an ignorant manager thinks that velocity==productivity.  What's to stop the manager from asking the team to "go faster" by finishing a higher story count each week?

      Seems like the root cause was never addressed, and that's sad.

      It's also funny that the guy the author quotes responds in the first comment to disagree with him.

      Charles Bradley
      Professional Scrum Trainer
      Scrum Coach-in-Chief

      From: Aeden Jameson <aeden.jameson@...>
      To: "scrumdevelopment@yahoogroups.com" <scrumdevelopment@yahoogroups.com>
      Sent: Friday, June 14, 2013 1:58 PM
      Subject: Re: [scrumdevelopment] User stories and relative complexity

      While I'm sure you'll eventually find what you want to. Here's something you may have not been looking for. 


      On Wednesday, June 12, 2013, Jesse Houwing wrote:
      I'm looking for a good book or article which explains the process of estaimating (and re-estimating) user stories using relative estimation/story points.

      Especially around backlog ordering, dependencies between stories and whether to take the benefits of re-use into account in this context.

      The stakeholder argues that in classic estimation he had much more insights into dependencies between stories and could thus plan his releases much better. He'd like the backlog fulle re-estimated each time the order changes or a dependent story changes.

      Instead of talking to the hand, I'd like some good whitepapers or practices that clearly explain the differences between the approaches one might take to relative estimation ans writing of story points.

      I've got a pretty good idea on how I'd like to do it, but I can't find the handholds to get this guy on board. He asked for readign material, so at least I have that :).


      GitHub: https://github.com/aedenj
      Linked In: http://www.linkedin.com/in/aedenjameson
      Blah Blah Blah: http://www.twitter.com/daliful

    • Show all 11 messages in this topic