Using RTC without teams?
We have small projects only about 20 members per each and we don't need separate project members into teams. Is there any reason why we should use at least one team with all same members as is in project? Or can we just use only project without creating teams at all if we don't need more than one team?
Is there like some reporting or source control aspect what we are missing if we don't use teams in one team projects. I know that in RRC and RQM there is no required to using teams.
|
2 answers
Ralph Schoon (63.1k●3●36●46)
| answered Jun 19 '13, 3:56 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Hi Simo,
some of the reports require at least one team area. You can work without having a team area, but these reports would miss required parameters. Some of the burnup and burndown reports are examples I have come across. You can use a project area for each of your projects. You can do it without a team area, but I would suggest to create a central team area for your team members in this case. Another approach (if you can live with the same process for all teams) would be to have only one project area. You can create a team area for each of your small projects. This would reduce administrative overhead compared to create project areas for each project. These two are the pattern that I have used. Comments I should have mentioned that it is good to have separate team areas for the projects if you use just one project area, because this would allow you to also separate concerns in planning per project. If you don't all the work items of all projects would be presented on one plan, even if you have separate categories for each project.
stuffing projects into one project area and managing the project by using team areas does improve upon the administration and even reporting for the projects.
There is no one-size-fits-all approach and there probably never will be.
|
Extract from help on this topic which answers your question
"Team areas are optional. A simple project with a small number of users might not need separate team areas. Instead, all work is done in the context of the project area." Here is the Link Comments 
Geoffrey Clemm
commented Jun 19 '13, 10:32 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The key phrase here is "simple project". In particular, if you don't need any of the features described in Ralph's answer, then you don't have to create a team area. So one approach is to just use the project area as your team area initially, and then when you encounter the need to have a team area, create one and move the team members from the project area down to the team area.
Geoffrey, please see my comment above ? any ideas?
1
Geoffrey Clemm
commented Jun 19 '13, 1:51 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You will probably want to start a separate question on your performance/scalability issues, since it is unlikely to be caused by using team areas vs. project areas. In particular, you'll want to identify specifically which operations are performing poorly. A performance problem that might be associated with using team areas instead of project areas is that some lists in the GUI can be against every object in the project area (independent of team area boundaries) such as streams and build engines. But there usually are filters you can apply (such as "only show me objects of that kind in team areas I belong to").
|
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.