It's all about the answers!

Ask a question

RTC & cross product Scrum teams


John McAuley (1111) | asked Apr 02 '15, 11:48 a.m.
Scrum teams are product agnostic, and projects want more flexibility to have people working on different product areas and different tasks.
RTC as it is now does not seem to support this ?

The "product backlog" is actually a team backlog as RTC has a 1:1 team to work category (filed against) mapping. This is a serious issue in that we can't have a true (one) product backlog and have teams working on different products. The backlog is based on what team owns items!
Granted people can be allocated % wise in their profile to different teams and hence different products, but given that will change VERY dynamically it's not a practical option.
How do people get around this with RTC ?

We want a Scrum team to be able to pull work into a Sprint from multiple product backlogs without RTC flagging that the person pulling the work item does not belong to the team area associated with the product category.

One answer



permanent link
Geoffrey Clemm (30.1k23035) | answered Apr 03 '15, 2:36 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The recommended way of modeling a product backlog in RTC is to have a particular top level iteration in a given timeline for holding the "backlog" for that timeline.   So the "product backlog" is not a (single) team backlog, but rather a backlog for any team that is using that timeline. You can also chose to use the backlog of one timeline as the backlog for other timelines, but there is not as much direct GUI support for this (for example, drag/drop in Quick Planner does not support this).

I didn't understand your comment about RTC flagging the person pulling the work item.  Can you give a specific example of the set of actions in a specific GUI that produce this warning/error, and a copy of the specific warning/error message you are getting?

Comments
John McAuley commented Apr 08 '15, 10:07 a.m. | edited Apr 08 '15, 10:11 a.m.

we have the backlog and timelines set up as you describe.
Team-1 associated with Product1 (category in RTC set up) category is what work items are filed against.
Team-2 is associated with product2.
Now if we want team-2 to help out on product1, a team-2 member can pull work filed against product1 into their next sprint, but RTC shows a yellow exclamtion warning against the team-2 member.
(not sure if this image will be visible)
Plus the work item will show up in Team-1 Sprint plan (filed against) even though the task is being done by someone in team-2.


Geoffrey Clemm commented Apr 09 '15, 12:18 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Remember that Filed-Against indicates what team should work on that work item, so if you want someone from Team-2 to work on a given work item, you either need to assign the Filed-Against of that work item to some category that is mapped to Team-2, or you need to add the appropriate members of Team-2 to Team-1.

Your answer


Register or to post your answer.