One team, multiple "projects"
We have a historical set up where a team work in different "projects" at the same time.
We have been struggling to get this "right" in RTC, but with limited success. As a much simplified example assume 1. three teams team 1..3 2. two "projects", "dev", "maintenance" Some of our attempts have been a. a shared iteration, where we have categories team1_dev, team1_maintenance, team2_dev etc mapped team team1..3 The above sort of works but doesn't quite feel right. It also breaks if the iterations are different between dev and maintenance. b. a shared iteration plus tagging Relying on tagging is a bit "loose". Having project info mixed with other possible tags is also a bit confusing. c. different timelines for dev and maintenance This feels like it should be the correct solution, but it appears to require splitting the teams which duplicates the team definitions. It also requires two plans which is sort of odd, as there is only one team. Are we missing something obvious? We are currently in RTC2 and is planning to move to RTC3 early next year. /Roger |
4 answers
For *most* teams, you are very close with answer C: different timelines for dev and maintenance.
You can either have one team assigned to both timelines, or create two teams. The later clearly identifies who is working on dev and who is on maintenance -- these users might overlap. Perhaps you could suggest your "ideal scenario" and we can work backwords to see how to do it in RTC? |
Ralph Schoon (63.5k●3●36●46)
| answered Jan 26 '11, 5:22 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Benjamin, Roger,
I am not aware of being able to have one team assigned to multiple timelines. In the team editor there is only one timeline association you could choose from. This implies to create separate teams for each timeline. There is a work item to overcome this restriction but I haven't seen any activities there lately. But I strongly agree option C would be the desirable solution. Both timelines can have a different Rhythm and separate teams. As you mention, the teams could have overlapping members and each member would have an assignment in terms of how much time is planned for each team membership. This works well with planning too. The overhead of creating seperate streams is minimal in case there is no complex team substructure that also needs copying. Ralph For *most* teams, you are very close with answer C: different timelines for dev and maintenance. |
We're in a similar situation except that we have six projects and only one logical team (though set up in RTC as one team per project for purposes of access control and reporting).
We're currently running a mix of a) and c) - five of the projects are lumped together in one timeline (four of them are small, so we can just about manually cope with the "real" timelines not matching up), and the sixth is in a separate timeline. However, all six projects use the same sprints. Neither of these approaches is ideal. a) can't handle the different "real" timelines properly, and throws off burndown reports, etc., and c) makes sprint planning difficult because we need to allocate resource across two different sprint plans (six if we do away with a)!). Our ideal would be if we could have sprints that span timelines, or at least sprint |
Geoffrey Clemm (30.1k●3●30●35)
| answered May 27 '11, 5:36 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Allowing a plan to span multiple timelines is requested in work item
94056. Please feel free to add a comment to indicate your interest/support. Until then, I believe you are using the available workarounds. Cheers, Geoff On 5/27/2011 8:08 AM, ideeley wrote: We're in a similar situation except that we have six projects and only |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.