Re: [scrumdevelopment] Re: Prioritization
- Ron Jeffries wrote:
> It's about being there all the time, not answering questions orExcept that most of their work involves other
> doing other team things all the time. See Alistair's $50,000 minute
> If they're as busy as you say, they need to be somewhere working.
> Might as well be somewhere near by.
people. Users. Marketers. Financers. Other stakeholders critical
to the success of the project. Who are not nearby. Often not even
nearby each other. This is the difficultly.
Alistair's calculation of a $50,000 per minute cost was a cool
way of explaining the importance of co-location. But it need not
only apply to the relationship between developers and the product
owner: it can also apply to the relationship between the product
owner and other people. Unless you have a product owner who
themselves knows all the right answers and has all the right
powers and who never needs to work with anyone but developers. I
have never seen such a product owner.
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.
- 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.