RE: [scrumdevelopment] Re: Kanban vs. Scrum
- Maybe companies only have one President because they can't afford to pay more than one person a $10 million salary and $25 million in performance bonuses, especially when the share price has dropped from $75 to $2.50 and the company has made a huge loss, and will either collapse, or depend on the government to bail them out. :) And of course because the share price has collapsed that President must be compensated a few million dollars to cover the loss of value in his share options, and in his pension plan.
Date: Sat, 1 Nov 2008 08:25:04 -0400
Subject: Re: [scrumdevelopment] Re: Kanban vs. ScrumRon Jeffries wrote:
> Does it strike you as an odd asymmetry that companies have oneVery interesting question.
> president but many workers?
But there are many ways in which to interpret it.
I think the issue is worth exploring a while.
It hadn't struck me as odd: mostly, I think, because I don't deal
with companies at that level. But now that you mention it, I do find it
Part of it comes from your wording.
One president, many workers. Instead, for example:
many executives, one electrician.
Maybe they are all workers, and the role of "president" only
requires one worker.
I'm a little unclear on the role of president anyway. Many
countries don't use the term in industry. And those that do use
it do not all use it in the same way.
And there are partnerships. And boards of directors, and other
forms of team leadership. Families. Sports teams. Some.
And of course things change over time. Many presidents, many
kings, many leaders.
But in some situations we persist in our desire for "one". So it
seems to me that the key question is: why do we sometimes have
this association between a single person, even in roles that
require more work than any one person can really do?
Lust for easy answers, even if wrong?
Love of hierarchy?
Monotheism? The divine right of kings?
Over to you, Ron. All of you.
- Wednesday, November 19, 2008, 3:05:08 PM, Dillon Weyer wrote:
> In this case how is XP different to Kanban then?XP differs from kanban in many of the same ways as Scrum. It
is batch pull, not continuous pull. Instead of a sprint, XP
calls it an iteration. In XP, like scrum, but not kanban, each
story has a high level estimate attached to it during release
planning, which is similar, but somewhat different from
backlog grooming in scrum.
> aacockburn wrote
> --- In firstname.lastname@example.org
> <mailto:scrumdevelopment%40yahoogroups.com> , Graeme Matthew <scrum@...>
>> Whats the difference between a product backlog and kanban they both
>> as signaling system to trigger action?
> The kanban is continuous pull, the backlog is batch pull.
> With the backlogs, each month you *promise* how much you'll do, and
> pull a *batch* of items from the product to the sprint backlog.
> You're now locked.
> With kanban, you pull directly from the product backlog to the
> work list, one at a time. There is no work estimate attached to the
> item - you just work on it till you're done, then pull the next.
> Some teams put size limits on the work list, so you can't work on
> more than e.g. 5 items at a time.
> That's quite a difference.