Re: [scrumdevelopment] Re: Kanban vs. Scrum
- Hello, Steve. On Saturday, November 1, 2008, at 10:40:33 AM, you
> Thinking about this some more, would the "point of contact" for theNot as I understand it. The SM makes few if any decisions. Her job
> team be the Scrum Master? While not the "Manager" isn't one role of
> the scrum master to facilitate team interactions (internally and with
> the PO)?
> While not quite the same as decision maker, I can imagine that, in the
> absence of the team coming to a decision, that the SM can be the one
> to narrow down the choices.
is to get the /team/ to make decisions.
You don't need to see my identification.
These aren't the ideas you're looking for. Move along.
- 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 email@example.com
> <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.