I know similar posts haven been made before, but let me add a slightly different perspective.
1) Sprints have to be associated with a milestone. I cannot even create a sprint without specifying which milestone it should belong to. 2) Stories are associated with sprints. Therefore, each story in a sprint is also associated with a milestone. In effect, this means that I cannot have a sprint in which work is done that belongs to two different milestones. I cannot, e.g., start work on feature X that is supposed to be released in October, if in that same sprint, I'd also like to finish work on feature Y that will be released in August. Maybe this is not a common situation, but for us it is the norm. So what we end up doing is that we define milestones that are completely meaningless, just because we need some sort of milestone to create sprints. So what I would like to suggest is this: disassociate milestones and sprints. Since requirements can be tied to milestones and stories are tied to requirements, the work for each milestone is documented along with those stories and there is no need to force sprints into milestones. -- 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
