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

52694Re: [scrumdevelopment] Story point estimating - ideal time vs relative scale

Expand Messages
  • Michael Jones
    Sep 27, 2011
      Hi Ron,

      Ah - I mean development items - the user stories are ballpark-estimated as they're added to the product backlog; then in the sprint planning meeting, they're decomposed by the developers into development items that make sense to them, and estimated by the developers at the same time.

      Is that nearer the mark?


      On Tue, Sep 27, 2011 at 2:39 PM, RonJeffries <ronjeffries@...> wrote:

      Hello, Michael,

      On Sep 27, 2011, at 9:34 AM, Michael Jones wrote:

      We're rolling out an agile process in my company, where waterfall processes have been used up to now. 

      I've been involved in a couple of discussions/debates with various folk here (a product manager and a fellow PM) about the units developers should use to estimate user stories in the sprint planning meeting. Specifically whether to use ideal time (e.g. "1 ideal hour"), or relative scale (e.g. "about the same as that registration form we did"). 

      I have my own views, but what are your thoughts? Are there any stand-out benefits of either in your experience? Should we throw it as an open question to our developers? 

      Why do you want to "estimate user stories in the sprint planning meeting"?

      Ron Jeffries
      I'm really pissed off by what people are passing off as "agile" these days.
      You may have a red car, but that does not make it a Ferrari.
        -- Steve Hayes

    • Show all 25 messages in this topic