On Aug 6, 5:52 pm, Ash <[email protected]> wrote: Hi Ash,
> I have made a Milestone backlog (equivalent to a release backlog in > normal Scrum) and I notice that tasks that don't have a sprint > assigned do not seem to show up, but those with one do. (Not 100% sure > this is the deciding factor, as a different bug currently prevents me > from assigning tasks to a sprint.) Normally in a Release Backlog we only put Requirement (declared as wish from the Product Owner) and the related User Stories that according to the team velocity will fit into the release cycle, and this is also only a guess. So if you plan requirement for a Milestone, all the stories not planned for any sprint, or planned for a sprint belonging to that milestone will appear in the Release Backlog. The tasks, being part of the Sprint, and totally under the responsibility of the team, are normally not included into a Release Backlog. Consider also the fact that this would mean to make up front planning of more than one sprint, probably at least three... not really Agile... ;-) > And yes, I have tasks and bugs as types that should show for the > milestone backlog. We never tested this, but ideally should work the same way as for the stories and the requirements, unless you changed the default configuration, in which case we will need your trac.ini file to have a look at the fields for the types and the types of ticket you created. HTH ANdreaT --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
