- ... I see where Robert is coming from here. Where does the PO get the information needed to be able to contribute as a PO for the team? They need to know whatMessage 1 of 224 , Nov 2, 2008View Source
>Robert, it sounds to me that you're describing someone who has too much
>to do effectively. Perhaps that personshould re-examine their role in
>all of the things they do, with an eyeto seeing where they have made
>themselves a bottleneck rather than afacilitator.
I see where Robert is coming from here. Where does the PO get the information needed to be able to contribute as a PO for the team? They need to know what might be required in the product, and understand the business value, and the impact key external events (such as product launches, trade shows etc). Acquiring this knowledge takes time – and it seems reasonable that’s sometimes going to take more time than explaining and discussing the same thing with the Scrum team.
They’re not a “mere conduit” for this information (in my understanding of Scrum, anyway).
- ... 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.