Re: [scrumdevelopment] Re: Prioritization
I'm interested in hearing more about PO's who do not
need to do many other things.
Can you give some examples?
Ron Jeffries wrote:
> Hello, Robert. On Saturday, November 1, 2008, at 2:10:34 PM, you
> > But I don't want to sound too negative: I think product owners
> > spending lots of time with developers is a good idea. In fact a
> > great idea. But if it is to be a lot of the time, like 100%, then
> > I think that either there needs to be a product owner team, or
> > things will go wrong elsewhere.
> There's nothing at all wrong with the PO having a team.
> That said, the need for the PO to do other things is very dependent
> on the specific product.
> Ron Jeffries
> I stand for excellence.
> I'm tired of people who stand for less. -- Mike Hill
- 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.