On Friday 02 July 2010, culliard wrote: > At the moment we don't really use it that way although developers > were suggesting they like to track progress of a component or sub > module e.g. whole GUI. To do that tasks would need linked to 2 'user > stories' - one for delivering value within sprints and other the for > component which could cross several sprints or even milestones. I > guess its like a component burndown but not sure what value this > would give to the team.
Depending on what you really need here, there may be other ways to achieve this than cumbersome "fake stories" for components or non- functional requirements. You could create a backlog that shows stories and tasks, but has a milestone scope. When you then add 'backlog_filter_attribute=component' in [agilo-general] you will see a drop down option on top of every backlog, allowing you to filter only see all tasks in a release that are for a specific component (GUI, ...). Cheers Robert -- 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
