Re: [scrumdevelopment] Re: Prioritization
- Fair enough: I suppose they must exist.
In our studies of agile teams, however,
my colleagues and I have never seen a project like this.
On 11/2/08, Ron Jeffries <ronjeffries@...> wrote:
> Hello, Robert. On Sunday, November 2, 2008, at 8:01:40 AM, you
>> I'm interested in hearing more about PO's who do not
>> need to do many other things.
>> Can you give some examples?
> Someone might be the PO for a single IT project. Or be in the early
> stages of inventing and envisioning some new idea. Or getting a
> program written to perform some technical calculation.
> It does happen.
> Ron Jeffries
> The central "e" in "Jeffries" is silent ... and invisible.
- 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.