On 21/06/2010, at 8:50 PM, Martin Häcker wrote: We are thinking about a way to achieve this without loosing the nice manual sorting. We're hesitant to go for clicking on headers to sort by that field as the interaction with drag'n'drop is complex. iTuens does it, but it's not very intuitive when drag'n'drop works and when it doesnt.
Perhaps a "Sort stories by Business-Value button" is actually the right aproach to ease this? (Feedback welcomed) I was thinking about it some more, and realised that this really only applies to requirements. The ability to manually sort stories within requirements, and tasks within stories, is really handy. So maybe an option to sort requirements by business value, as you suggest, would be all that is needed. I do however feel that using the Business-Value for sorting is actually abusing it, as the business-value shouldn't change if you want to re-order stories so while it robs you of some functionality I think that's actually a change for the better to reflect the real business value in that field. I hadn't really thought of it like this. I guess it largely depends on how people use the business value. The way we use it (largely because of how it worked prior to 1.3, and hence how we started using it), is that if a requirement becomes more or less important for a client/stakeholder then it has a greater or lesser business value for us (after all it is the clients that pay the bills :-)). I guess the case could be made though, as you say, that the business value and priority aren't directly related. I wonder then if it is actually the ROIF that is more important to prioritising. Logically it does make sense to do a requirement with business value 100 and total story points of 1 and hence roif of 100, before one with business value 2000 and total story points of 200 and hence roif of 10. The only problem with this in our case is that we have tended to be lazy by only adding stories and/or story points, for higher business value requirements, as we are not likely to get to the lower ones anytime soon, so it seems silly to plan them too much. We should probably add them all though, as now I see that not having them is reducing our ability to prioritise effectively. So if the option could be extended to sort requirements by business value and/or roif then it would give people to flexibility to use it in slightly different ways depending on how they wish to do things. As a developer myself (as no doubt most people using your product are :-)), I am well aware however that you can never please everyone, and that often what the users of a system think they want, isn't what they actually want, and that often there are better ways. The tricky thing is usually getting them to accept a change. As such I am open to other options, and will even adapt to the current method if necessary. Chris Manning Integrated POS Solutions -- 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 agile42 GmbH <http://www.agile42.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
