> The problem with this approach is that it's hard to create a team > backlog (you create a giant tracker?), plus tracker issues don't allow > you to prioritize what do you do in each sprint.
Backlog = whole RedMine (all Feature items that are not associated with any "sprint" tracker). > With target versions, you can easily gather the stuff the team has done in a > sprint (automatically), see what's 'ready for testing' and should be > done in the next sprint, and you can prioritize your backlog of redmine > issues. Indeed that's nice, but that was created for version management, not scrum management. > Also the redmine-backlogs plugin doesn't integrate with that - > http://projects.theforeman.org/rb/master_backlog/ - which makes > prioritization and moving stuff from one sprint to another easier. With > a tracker moving stuff from sprint to sprint would mean creating a new > tracker? Yes, I mean exactly that. But no moving from "backlog", see above. And this plugin - it kills our instance the moment we start drag and dropping. This whole scrum game miss one particular aspect - agility. Please, can we please not create these crazy "backlogs" and the dance around and just use RedMine as it was design for? Otherwise we will be doing nothing but tossing tickets from backlog to backlog. * Put an item on "backlog" = create new Feature, NEW state * Put it on "sprint" = associate with feature issue (*) * Resolve issue, set Target Foreman version we ship it into * Profit! (*) or use Target version if you really think it's any benefit -- Later, Lukas #lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
