On 20 Jul, 2009, at 9:46 , Fabrice Pipart wrote: > Thanks for the quick (and precise) answer ! YAW :-)
> On Jul 18, 2009, at 12:25 PM, Andrea Tomasini wrote: >>> >>> 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 :-) > Why wouldn't you consider it Scrum? Because in Scrum the responsibility to pick bugs, or plan tasks is of the Development Teams, so there is no reason why a Product Owner would try to plan bugs or tasks into a release backlog. The Development Team is responsible for the Product Quality and as such in charge of making sure that there are as "few" bugs as possible. Thinking Lean will push the Team to "Stop the chain" and first fix the process that generated the bug - read, write unittests and functional tests to reproduce the bug automatically - and than fix the code - read work against the tests and fix the issue - in this way you will have a guaranteed coverage also for no regression :-) Related to the Tasks in particular, a Scrum Team should plan "Just Enough & Just in Time..." so there shouldn't be tasks moving around from one Sprint to the next, when the Sprint is over, the tasks are not needed anymore, being by definition all the "actions" that the Team consider useful to transform the committed functionalities into "potentially shippable" product increments by the end of a Sprint. But we are all humans, right? So what we normally do in Agilo, we retarget the tasks that we consider still useful - normally related to the infrastructure or tooling that the Team build and maintains - at the end of a Sprint, directly in the next Sprint Backlog (go to Sprint, in Roadmap, chose the sprint, and press "Close": this will save the final velocity of the Team in the Statistics - calculated as all the story points of all closed stories in the sprint, and will ask you if you want to retarget the left Open Tickets into the next Sprint). >>> 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. > > I prefer not to remove some "business rules" I am probably using > without even realizing it. Than I suggest you stick to the Agilo scope than, and keep Requirements planned to Milestones (Releases) and Stories and Tasks to the Sprint. >>> 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? > > This is what I did and it seems OK. > This means picking items from two different places during the Sprint > planning meeting (Release Backlog and Release Defect Backlog) but this > is OK. Yes, ideally the Team should manage the Bug Backlog their own, being responsible for Quality :-) What we always teach to our coached team is to try to understand the "root cause" of a Bug, when it happens, and try to define action to avoid that type of bug to happen again, when possible automating, when not, setting a best practice and link it to the definition of Done :-) > Thanks again for the precious help ! YAW > Fabrice 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 -~----------~----~----~----~------~----~------~--~---
