Hi Martin and others,
there seems to be more than one way of doing things within Agile/Scrum. We
seem to use one of those... ;-)
For us
- the BL is the place to keep *all* stories for the product (i.e., it is
very long)
- we evaluate stories with custom variables (business value, technical
value, general risk) and use a bit of math to combine them into a story
priority - no manual sorting involved, needed, or wanted
- we use milestones are used to structure stories over longer time
periods (i.e. a story has a high business value, but PO decided the feature
is for next year's release)
For us, *sorting the backlog* by story priority *is a mandatory feature*
(preferably
by any presented attribute). So far, we have been using customized reports
with big sql statements to get the sorted backlog. But the report does not
provide the very useful in-line/in-table editing of story properties.
Since a short while, we compute the priority automatically in the database
via a trigger on ticket_custom and are now able to se the priority (and how
its changing) directly in to BL view - change any of the evaluating values
and the priority updates with it. Now it's just the automatic sorting that
is missing.
For us, the drag-n-drop of stories looks very cool, but is of no practical
use - but - as said earlier - use cases differ.
Another thing I would really *love in the BL* is to have a place to
- enter minimum, average, and maximum stories our team processes per
sprint
- enter a number N of sprints into the future
and get the backlog with stories colored in green, yellow, and red for
stories that will be, will most likely be, may be, and will certainly not be
implemented
within the next N sprints (sum of story points of ordered backlog is
0...N*min, N*min..N*average, N*average..N*max, >N*max). That's a great tool
to show the PO what consequences *forcing up a story* has. In a spread
sheet, this is very easy to do, but I hate the tedious and error-prone
trac-export, excel-import, resort, trac-re-import steps.
For the mentioned difficult interaction between drag-and-drop (dnd) and
sorting I would suggest to run the BL in eiher of two modes
1. manually sorted with dnd freely available (two-state button or
checkbox indicating the feature)
2. automatically sorted by any attribute. Attempting dnd would keep the
current sorting and switch back to manual. Because this would loosing the
previous manual sorting, this operation could be protected by a query to the
user
Regards,
Hartmut
--
Follow Agilo on Twitter: http://twitter.com/agiloforscrum
Please support us by reviewing and voting on:
http://userstories.com/products/8-agilo-for-scrum
http://ohloh.net/p/agilo-scrum
http://freshmeat.net/projects/agiloforscrum
You have received this message because you are subscribed to
the "Agilo for Scrum" Google Group. This group is focused on
supporting Agilo for Scrum users and is moderated by
Agilo Software GmbH <http://www.agiloforscrum.com>.
To post to this group, send email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo
