Rudiger,
Sorry for the delay. I've been up to my *^%$% in alligators so I've
been delayed in draining the swamp.
What you state IS workable. We do not move the finished Stories to
a review queue, we just added a Ticket Status of QA testing. We run our
queries accordingly and review the
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)
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
Ken Crocker wrote:
Rudiger,
I'm not sure what you mean when you refer to SCRUM.
http://en.wikipedia.org/wiki/Scrum_(development)
P.S. I hate scrum :/
--
--
Tom Lahti
BIT Statement LLC
(425)251-0833 x 117
http://www.bitstatement.net/
--
Tom,
Thanks for the link. After reading the info, I believe that RT could
/easily/ be used to promote such a process. Some terms would have to be
re-named or their meaning translated, but the overall process design is
VERY similar to what we do now in our organization. I have developed
Ok Thanks for your feedback.
Scrum in 5 minutes
http://www.softhouse.se/Uploades/Scrum_eng_webb.pdf
Based on what you say it seems like the following might work.
Each project/team has a BACKLOG QUEUE of stories(requirements). The
product owner regularly prioritizes them.
During the fortnightly
