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

Re: [scrumdevelopment] Re: Agile Estimating and Planning - Story Points

Expand Messages
  • scrum@contrado.com.au
    Dave I am kind of leaning the same way in that relative effort in hours seems to be easier to convey especially for outsiders. Regards Graeme ...
    Message 1 of 6 , Jul 24, 2006
      Dave

      I am kind of leaning the same way in that relative effort in hours seems
      to be easier to convey especially for outsiders.

      Regards

      Graeme

      > --- In scrumdevelopment@yahoogroups.com, "scrum@..." <scrum@...> wrote:
      >
      > > For example:
      > > PRODUCT BACKLOG
      > >
      > > Story / Description Est (Story Point)
      > > As a user i login to the system 5
      > > As a user i can logout from the system 1
      > >
      > > Now what happens when the PO reports a high priority bug so we now have:
      > >
      > > Story / Description Est (Story Point)
      > > As a user i login to the system 5
      > > As a user i can logout from the system 1
      > > Fix profile screen bug that causes timeouts
      > >
      > > This is where im confused as to where story points fit in. How do I
      > > apply story points to this item?
      >
      > In this case I'd treat this defect as just another type of user story.
      > You'll need to estimate the time it will take to find the root cause
      > and resolve it based on the team's understanding of the problem.
      >
      > So in your example, I'd determine how much effort the bug would take
      > compared the the other stories. Is it twice as big as the Login
      > feature? Maybe half the size? The Story Point system is a good way
      > to specify size without implying a duration for release planning.
      >
      > Having said that...
      >
      > Personally, I don't find story points as useful in iteration/sprint
      > planning , since you're generally estimating at a finer-grained level
      > of detail, where in release planning it's a pretty high level estimate
      > to help with the prioritization proces.
      >
      > Since most defect fixes tend to be scheduled at the sprint planning
      > level (in my own experience), you may just want to skip the story
      > points and use ideal days/hours in your estimates for these.
      >
      > Your mileage may vary.
      >
      > --Dave
      >
      > David Churchville
      > http://www.extremeplanner.com/blog
      >
      >
      >
      >
      >
      >
      > To Post a message, send it to: scrumdevelopment@...
      > To Unsubscribe, send a blank message to:
      scrumdevelopment-unsubscribe@...
      > Yahoo! Groups Links
      >
      >
      >
      >
      >
      >
      >
      >
      >

      --
    Your message has been successfully submitted and would be delivered to recipients shortly.