Rudiger,
I'm not sure what you mean when you refer to "SCRUM". However, we ARE supporting many software applications with technical support teams and Queues oriented for each application/team. We have 1 queue specifically designed to act as the initial request Queue where tickets are reviewed and prioritized, then (if approved) moved to the queue that supports the application the ticket is asking work for. For example, one large support group, Financial, supports all the various software dealing with our financial organizations and they have 12 different queues for that activity. There are, consequently at least 24 different groups, where each queue has a user group that WORKS on the tickets and another that is allowed to CREATE tickets (some that have the same members). Our structure for privileges is rather tight (only a couple for "Priviliged" Users. Mostly Queue-oriented)) that allow for keeping tickets secure (only the OWNER and the Queue Manager can Modify a Ticket) within their queue. We also have a QA Workflow process that ensures our standard for QA Approval is followed before a ticket is allowed to be "QA Approved" and then Resolved (for example, we NEVER allow the ticket owner to QA Approve their own work). A separate user from the QA Approval group are the only ones with privileges to modify the CF that is used to indicate QA Approval. Anyway, that's pretty much a summary of how we do things. If the details of any of this will help you, then I'd be glad to share how we do it. Kenn LBNL On 3/19/2009 10:45 AM, Rüdiger Wolf wrote: > Hi All > > I was hoping to get some feedback from users who are using RT to support > software development teams when using SCRUM approaches to planning work. > > We several project teams and keeping people allocated to project for > several months at a time. > We track work based on several tasks (child) related to single story > (Parent). > We also track impediments. > Use two week long iterations. At the end of iterations there are > sometimes several stories and tasks that need to be moved into the next > iteration. Stories (and related tasks) need to be moved from a backlog > queue to the current iteration. > > I would like a project team members to look at stories (sorted by > priority) and related tasks for the current iteration and take ownership > of tasks. > Team would like to quickly answer/update tasks in order to provide > answers for stand-up questions. What did you do yesterday? what are you > doing today? > > I would like to be able to report on story, task and impediment > life-cycles for project and iterations. > I see that there is talk of a REST style interface so I assume that one > could write script to extract issue data quite quickly. > I could then create burn down charts etc. as required from the extracted > data. > > One feature I REALLY like in our current system is the ability to export > stories/tasks/impediments to excel. > Update values in excel. > Next one uploads stories/tasks/impediments back into the tracker via web > interface. > I see that there is a possibility of creating and updating in bulk via > the web interface. > > Thanks for your comments. > > Regards > Rudi Wolf > _______________________________________________ > http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users > > Community help: http://wiki.bestpractical.com > Commercial support: sa...@bestpractical.com > > > Discover RT's hidden secrets with RT Essentials from O'Reilly Media. > Buy a copy at http://rtbook.bestpractical.com > > _______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: sa...@bestpractical.com Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com