I am looking for someone to help explain the relationship that milestones play with Agilo.
I notice that I can assign a requirement to a milestone, but when I do it doesn't get displayed any more in the product backlog. What does a milestone represent? I am trying to work out what the best way to represent different areas of activity? We have more than one thing going on, have requirements for each. In any one iteration the team might be working on user stories from any of these. I've used Hansoft in the past, and they break the backlog into a hierarchical tree, which makes it easy to have separate branches for each activity. In agilo the backlog appears essentially linear. I can imagine setting this up in any of the following ways: * Use separate product catalogs for each area of activity. * Use milestones as the top level idea, and make sure all activity is bound to a relevant milestone. * Extend the trac system to add an additional 'tags' field to each ticket and track using that. If you are using agilo in this way, I'd be very grateful if you could share with me how you manage it. Many thanks, Joe --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
