On 17 Jul, 2009, at 18:02 , Fabrice Pipart wrote:
> Hi all ! Hi Fabrice :-) > Here is a behavior I have with my setup and cannot understand. > I created a Release backlog which contains all the requirements, > stories, bugs and tasks for a Milestone. > The backlog displays fine. > > I have a milestone field for requirements, stories, bugs and tasks. > I consider useful to be able : > - to assign a Bug (not linked with any Story nor requirement) to a > milestone (even if I dont know yet in what Sprint it will be fixed) > - to have some Tasks linked to that bug which is not linked to > anything That is possible, I wouldn't consider it Scrum... but Agilo can do it :-) > The problem is that when I am in my Release Backlog, if I do a > change for example in the Sprint column (when I prepare a Sprint), > then all my Bugs not linked with a Story and the underlying Tasks > loose their Milestone property : > > * milestone: Release 1.3.2 => > > Is this a bug? > Is there any workaround? I suspect it is due to the "business rule" Sync Milestone and Sprint, which is there to guarantee hierarchical consistency between Sprint and Milestones assignments. You can try to disable this, you will find it in the Admin/Plugins/Agilo, should be SprintAndMilestoneSync rule. The reason why it behaves like this is that Agilo tries to implement "ownership" by scope, which means, small and fine grained items will belong to Sprints, and Requirements will belong to Milestones, which represent releases. The idea behind is that Scrum delegates to the Teams to choose the amount of work to do in a Sprint, so they will pull stories and bugs according to the given backlog prioritization. "Thinking Lean" also implies that the tasks are broken down only shortly before being done, that is the most efficient way to have clear ideas and more accurate estimations. The release Backlog it is normally used to plan the value for a Release, which is represented by Requirements. So the POs plans the requirements they would like to see into a product release, and the linked stories, not explicitly planned for sprints outside of the Milestone will appear in the Backlog as linked items. This will allow the POs to monitor the status of completion of a Release, and manage the risk and the expectations better :-) > This is extremely inconvenient since I could loose some Bugs to > solve in the upcoming release. Why you do not just create a Bug Backlog? And let the teams pick out of it at the Sprint Planning meeting? > Best regards HTH Best 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 -~----------~----~----~----~------~----~------~--~---
