Loading ...
Sorry, an error occurred while loading the content.
Skip to search.
 

Re: [scrumdevelopment] Re: Burn down chart goes up

Expand Messages
  • George Dinwiddie
    Jack, How often do you change the scope of the in-progress sprint? - George ... -- ... * George Dinwiddie * http://blog.gdinwiddie.com
    Message 1 of 105 , Jun 12, 2009
      Jack,

      How often do you change the scope of the in-progress sprint?

      - George

      jmilunsky wrote:
      > Hi George,
      >
      > So sorry I baled as it was getting interesting. I was working on a client proposal with a really tight deadline. I promise I wasn't ignoring you.
      >
      > My responses below...
      >
      > --- In scrumdevelopment@yahoogroups.com, George Dinwiddie <lists@...> wrote:
      >> Jack,
      >>
      >> Did you miss these questions? Or are you ignoring me?
      >>
      >> - George
      >>
      >> George Dinwiddie wrote:
      >>> jmilunsky wrote:
      >>>> Why do u have a problem with this?
      >>> What problem? I asked you a question.
      >
      >>From your line of questioning it sounded like you were suggesting I was crazy.
      >
      > The way you describe it is fairly accurate.
      >
      > We as a team look at the burndown everyday. It's just another datapoint for us. We breakdown user stories into tasks as prescribed in the Sprint planning meeting (2nd half). We do either 1 week or 2 week sprints. So our task breakdown is fairly detailed. Each of these tasks is estimated in hours. And each day our developers re-estimate in progress tasks. This takes them all of 2 minutes each day.
      >
      > It's not like being behind is such a big deal but we try our best to get our teams on a stable velocity trajectory and overall we have done pretty well.
      >
      > Our company manages many projects and so for me, i scan through all the burndowns daily and relatively quickly i have a good sense of where things are at.
      >
      > Thought leaders such as Ken Schwaber and Mike Cohn.
      >
      >
      >>>> I don't know why you would think that this is so out to lunch
      >>>> especially since this is prescribed by all scrum thought leaders
      >>> Tell me a little more about this practice. As you briefly described it,
      >>> it sounds something like this:
      >>> 1. Project Manager looks at whether the burn down chart is above or
      >>> below the rhumb line.
      >>> 2. Project Manager talks with the Product Owner to change the scope of
      >>> the in-progress Sprint.
      >>>
      >>> Is this an accurate elaboration? Can you give more detail?
      >>>
      >>> And who are "all scrum thought leaders" that prescribe this?
      >>>
      >>>> I assume you don't use a burndown?
      >>> You assume wrong. I don't, however, use it in that fashion.

      --
      ----------------------------------------------------------------------
      * George Dinwiddie * http://blog.gdinwiddie.com
      Software Development http://www.idiacomputing.com
      Consultant and Coach http://www.agilemaryland.org
      ----------------------------------------------------------------------
    • George Dinwiddie
      Jack, How often do you change the scope of the in-progress sprint? - George ... -- ... * George Dinwiddie * http://blog.gdinwiddie.com
      Message 105 of 105 , Jun 12, 2009
        Jack,

        How often do you change the scope of the in-progress sprint?

        - George

        jmilunsky wrote:
        > Hi George,
        >
        > So sorry I baled as it was getting interesting. I was working on a client proposal with a really tight deadline. I promise I wasn't ignoring you.
        >
        > My responses below...
        >
        > --- In scrumdevelopment@yahoogroups.com, George Dinwiddie <lists@...> wrote:
        >> Jack,
        >>
        >> Did you miss these questions? Or are you ignoring me?
        >>
        >> - George
        >>
        >> George Dinwiddie wrote:
        >>> jmilunsky wrote:
        >>>> Why do u have a problem with this?
        >>> What problem? I asked you a question.
        >
        >>From your line of questioning it sounded like you were suggesting I was crazy.
        >
        > The way you describe it is fairly accurate.
        >
        > We as a team look at the burndown everyday. It's just another datapoint for us. We breakdown user stories into tasks as prescribed in the Sprint planning meeting (2nd half). We do either 1 week or 2 week sprints. So our task breakdown is fairly detailed. Each of these tasks is estimated in hours. And each day our developers re-estimate in progress tasks. This takes them all of 2 minutes each day.
        >
        > It's not like being behind is such a big deal but we try our best to get our teams on a stable velocity trajectory and overall we have done pretty well.
        >
        > Our company manages many projects and so for me, i scan through all the burndowns daily and relatively quickly i have a good sense of where things are at.
        >
        > Thought leaders such as Ken Schwaber and Mike Cohn.
        >
        >
        >>>> I don't know why you would think that this is so out to lunch
        >>>> especially since this is prescribed by all scrum thought leaders
        >>> Tell me a little more about this practice. As you briefly described it,
        >>> it sounds something like this:
        >>> 1. Project Manager looks at whether the burn down chart is above or
        >>> below the rhumb line.
        >>> 2. Project Manager talks with the Product Owner to change the scope of
        >>> the in-progress Sprint.
        >>>
        >>> Is this an accurate elaboration? Can you give more detail?
        >>>
        >>> And who are "all scrum thought leaders" that prescribe this?
        >>>
        >>>> I assume you don't use a burndown?
        >>> You assume wrong. I don't, however, use it in that fashion.

        --
        ----------------------------------------------------------------------
        * George Dinwiddie * http://blog.gdinwiddie.com
        Software Development http://www.idiacomputing.com
        Consultant and Coach http://www.agilemaryland.org
        ----------------------------------------------------------------------
      Your message has been successfully submitted and would be delivered to recipients shortly.