RE: [scrumdevelopment] Re: Product Backlog questions
- Great, You get to write the backlog chapters of the next book!
From: gilmanj_2000@... [mailto:gilmanj_2000@...]
Sent: Friday, November 30, 2001 2:41 PM
Subject: [scrumdevelopment] Re: Product Backlog questions
Now I think I get it!
--- In scrumdevelopment@y..., "Ken Schwaber" <ken.schwaber@v...>
> <First, you say that "the 'current product backlog' represents work
> that will be done against the rooot of the source library."
> I was under the impression that the product backlog represented both
> work that will be done and work that "might" be done. However,
> release backlogs and sprint backlogs represented only work to be
> done. Is that incorrect?>
> Product Backlog is a single list of work that might be done.
> indicate where we think the next Sprint might come from, the Sprintafter
> that, etc., and another separator indicate that moment's plans forthe next
> release. But the order and the separators move around as thebusiness
> changes its mind because of market conditions or project progress.As
> product backlog is completed in a Sprint, it is removed from theproduct
> backlog (already done), or when it is selected for and being workedon in a
> current Sprint, it is marked and doesn't move until the end of theSprint
> (when some of it might be not completed and need to be reenteredinto the
> Product Backlog. Sprint backlog is a separate list, and the onlyother
> separate list of work.these
> <Second, how do you represent what is workable versus unworkable in
> the product backlog, or are you saying that items are moved out of
> the product backlog onto a release backlog and/or(?) sprint backlog,
> and not simply replicated in these lists, and it is at this point
> that said work becomes workable because you don't move items to
> lists until you have put a sufficient level of thought to how theycurrent
> will be done?>
> Put a flag in a product backlog columns ... completed, pending,
> sprint, issue. The issues are unworkable backlog because they needto be
> turned into work.addition
> <<.S. I think this adds to my earlier comment that a valuable
> to the book would be sample artifacts showing their contents andarchitectural
> relationships to each other>
> I agree.
> > The current product backlog represents work that will be done
> against the
> > current root of the source library. Major functional,
> > design flaws are represented in this list, along with new
> > Like, we need to add additional indices to the workflow system
> because of
> > performance problems. Issues are in the product backlog, but they
> don't yet
> > represent work (unworkable backlog). For instance, an issue might
> be that
> > the workflow has inadequate performance for the volume of expected
> > This isn't yet work (unworkable), but when it is thought about and
> the work
> > that will address it known (add more indices), the issue is
> and thehttp://docs.yahoo.com/info/terms/
> > work (indices) is in the backlog.
> To Post a message, send it to: scrumdevelopment@e...
> To Unsubscribe, send a blank message to:
> Your use of Yahoo! Groups is subject to
To Post a message, send it to: scrumdevelopment@...
To Unsubscribe, send a blank message to:
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/