... Just pondering this for a while, it occurs to me that a point of distinction might be the relationship between the PO team-member who sits with theMessage 1 of 224 , Nov 2, 2008View SourceRon Jeffries wrote:
> There's nothing at all wrong with the PO having a team.Just pondering this for a while, it occurs to me that a point of
distinction might be the relationship between the PO team-member
who sits with the developers, and those who do not.
I guess in Scrum terminology, the PO would by definition be the
one who is there, and other people are not the PO. And it is the
PO, the who is with the developers, who has the power and
responsibility to make business decisions about the software.
In another possible approach, the power and responsibility might
be elsewhere. This is more common, I think, on large engineering
projects: ship-building, for example. The client has a
representative present, but they are there mostly to observe and
This reminds me a little of a distinction I understand exists
between passenger trains and passenger aircraft. On trains, the
conductor is in charge overall, and communicates with the driver
who is responsible for operating the equipment. On aircraft, one
person is in charge of both.
So, um, if a software development team were a machine, then would
the agile PO would be, um, more like:
a) train conductor
b) train driver
c) aircraft captain
... 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 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.