On Wednesday 02 June 2010, jcperron wrote:
> As I see the new version (0.9.0.1) don't have any sorting button. I
> work with a product backlog containing more than 400 tickets on 15
> components, using the drag and drop to sort all this is almost
> impossible. Do you have any suggestion or work around ?
The general idea would be to introduce scoped backlogs. One team can
probably not pull from a 400 item backlog anyway. If they are only
interested in stories for one component, they have to go through all
stories even of other components, thus wasting time.
If you create a milestone for each component (or maybe a group of
components), and add the milestone field as a visible field for
stories/requirements, you can split your 400 item backlog into several
backlogs where items for different components/groups are prioritized.
This would make sorting easier, and also ease selection of items for the
team(s).
Does this help you?
Robert
We removed automatic backlog sorting because it was flawed in some areas
and confused many users:
1. "default sorting" and manual drag&drop interact in strange ways,
it's impossible to find out automatically which one should have
preference...
2. In the new backlog you can drag&drop containers with all items below
them so there should be less items to drag.
Also from a Lean point of view there is a maximum number of items that
make sense in a backlog. Usually you have only user stories for the next
1-2 sprints and containers (requirements, MMF, themes) for the next
release or two (depending on your setting).
The backlog should be a tool, not an ever-growing ticket-storage. Keep
it managable. :-)
fs
Am 18.03.11 16:30, schrieb nescha:
> You should remove from Help all feature descriptions that aren't present
> any more. I lost an hour trying to find "Calculate" button. There are
> many hours lost because of this and this ain't good scrum practice ;)
Indeed removing that reference seems like a plausible response. :)
Can you give me the exact location where you still found the reference?
I'll remove it ASAP then.
Regards,
Martin
[x] done.
Thanks!