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

Re: [scrumdevelopment] Re: Adding up the hours for the burndown

Expand Messages
  • Ron Jeffries
    ... Your ScrumMaster should be defrocked. Ron Jeffries www.XProgramming.com Thousands of years ago, the first man discovered how to make fire. He was probably
    Message 1 of 10 , Jul 28, 2006
      On Friday, July 28, 2006, at 10:52:30 AM, aefager wrote:

      > I had a bad experience with this. Our ScrumMaster decided that since
      > we were already updating the burndown, that the daily meeting was not
      > needed. Instead, I had to go to the whole team and get by email what
      > they were working on, remind them to update the burndown, and what
      > they got done yesterday, merge it into one email, and send that out
      > to all the chickens. Two hours of hunting and fetching, instead of a
      > 15 minute meeting, because the SM was in a different building and
      > running multiple scrums at once. I did not feel very agile, and it
      > started due to the burndown not being a part of the Daily Scrum
      > Meeting. A horror story and an extreme case, I hope, but still, the
      > chance to see the numbers drop all together in one meeting is a boost
      > that I missed.

      Your ScrumMaster should be defrocked.

      Ron Jeffries
      www.XProgramming.com
      Thousands of years ago, the first man discovered how to make fire.
      He was probably burned at the stake he had taught his brothers to
      light - Howard Roark (The Fountainhead, Ayn Rand)
    Your message has been successfully submitted and would be delivered to recipients shortly.