Re: [scrumdevelopment] Per Person Burndown Poll Doesn't Make Sense
Hello, captwilco2002. On Monday, August 11, 2008, at 12:11:21 PM,
you wrote:
> 1. Why doesn't the poll make sense?
Because ...
... per person tracking is counter-productive;
... per person tracking does not collect useful data;
... burndown is measured in things done, not time spent;
... people don't burn things down, teams do.
> 2. Do you think I should be tracking this?
No. Not remotely.
> 3. About how many hours can be expected for an individual to burndown
> in one day (on average)? (Not what is a reasonable number of hours to
> expect each person to burndown on a daily basis, hence the purpose of
> my poll)
What is the difference between an average number that can be
expected, and a reasonable number to expect?
But never mind. Tracking individual hours of anything will break
Scrum, or any other process.
Ron Jeffries
www.XProgramming.com
I once had a coworker who worked so hard that when I came in the
morning, he was already sitting there trying to fix the things he
broke after I left the day before ... -- Ilja Preuss.
[reposted from http://groups.yahoo.com/group/scrumdevelopment/message/31661 by mj]
Re: [scrumdevelopment] Per Person Burndown Poll Doesn't Make Sense
Hello, captwilco2002. On Monday, August 11, 2008, at 12:11:21 PM,
you wrote:
> 1. Why doesn't the poll make sense?
Because ...
... per person tracking is counter-productive;
... per person tracking does not collect useful data;
... burndown is measured in things done, not time spent;
... people don't burn things down, teams do.
> 2. Do you think I should be tracking this?
No. Not remotely.
> 3. About how many hours can be expected for an individual to burndown
> in one day (on average)? (Not what is a reasonable number of hours to
> expect each person to burndown on a daily basis, hence the purpose of
> my poll)
What is the difference between an average number that can be
expected, and a reasonable number to expect?
But never mind. Tracking individual hours of anything will break
Scrum, or any other process.
Ron Jeffries
www.XProgramming.com
I once had a coworker who worked so hard that when I came in the
morning, he was already sitting there trying to fix the things he
broke after I left the day before ... -- Ilja Preuss.