- Hello, Steve. On Sunday, November 2, 2008, at 10:45:48 AM, you ... I m not comfortable with the SM being an information conduit. It s at least one rail moreMessage 1 of 224 , Nov 2, 2008View SourceHello, Steve. On Sunday, November 2, 2008, at 10:45:48 AM, you
> Yes, that was my point. The team MAKES the decisions. The SM can beI'm not comfortable with the SM being an information conduit. It's
> the point of contact, is also the one to help those decisions get
> made. In some ways analogous to the committee of product owners.
> (though not exactly the same). With all of those caveats, what I said
> was probably not helping the discussion ;)
at least one rail more than is needed.
I know we always like to say it'll be easier to do it now than it
will be to do it later. Not likely. I plan to be smarter later than
I am now, so I think it'll be just as easy later, maybe even easier.
Why pay now when we can pay later?
- ... 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, likeMessage 224 of 224 , Nov 19, 2008View SourceWednesday, 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.