designing RTC project areas for large organizations?
Accepted answer
we have 2 PA,
- Scrum based (10 users, us)
- Formal process model - ~400 users and increasing
Advantages of using 1 PA for one process
- Same process across the board
- Sharing components are easier
- Query for workitems across products since (in RTC 4.0.5) it's not possible to create queries which searches across Project Areas
-
Disadvantages of using 1 PA for one process:
- Different process for different team, which obviosuly shouldn't be the case but some time these exceptions arise where they want to share components and follow different process models
- When the PA inheritance is broken, it is more work to add changes everywhere
- difficult to set permissions for components (viewing & hiding. See https://jazz.net/forum/questions/150465/how-to-setup-streams-with-different-access-control-to-components-for-external-access)
- More discussion with all stakeholders in order to convince if there was a request for process deviations only for a team or 2
We have around 400+ users and increasing
Some more for your reading:
https://jazz.net/forum/questions/150465/how-to-setup-streams-with-different-access-control-to-components-for-external-access
https://jazz.net/forum/questions/151675/single-project-area-constraintsdisadvantages
- Scrum based (10 users, us)
- Formal process model - ~400 users and increasing
Advantages of using 1 PA for one process
- Same process across the board
- Sharing components are easier
- Query for workitems across products since (in RTC 4.0.5) it's not possible to create queries which searches across Project Areas
-
Disadvantages of using 1 PA for one process:
- Different process for different team, which obviosuly shouldn't be the case but some time these exceptions arise where they want to share components and follow different process models
- When the PA inheritance is broken, it is more work to add changes everywhere
- difficult to set permissions for components (viewing & hiding. See https://jazz.net/forum/questions/150465/how-to-setup-streams-with-different-access-control-to-components-for-external-access)
- More discussion with all stakeholders in order to convince if there was a request for process deviations only for a team or 2
We have around 400+ users and increasing
Some more for your reading:
https://jazz.net/forum/questions/150465/how-to-setup-streams-with-different-access-control-to-components-for-external-access
https://jazz.net/forum/questions/151675/single-project-area-constraintsdisadvantages
One other answer
I have seen following scenarios
For an organization that has thousands (2Kto 3K CR's per year) of change request, where each CR runs from 15 day to 1 year and they require a project plan for implementation we implemented Single project area with multiple teams ( representing groups by application owners) and a phase plan for each change. This could have been also managed through a seprate Project area per CR, but the complexity of team structure (Team area maintenance) and admin overheads, we had to limit it to single project area.
In another organization (product development) we created a seprate project for each product and its variants and even kept one project per RTC instance to avoid performance issues . The consideration here was large number of SCM streams and components and number of users and size of SCM artifacts, access control requirements.
In my understating the decision would depend on
1. Dependency of project on each other
2. number/ volume of artifacts (SCM / Workitems)
3. number of plans - Project team structure
4. Access Control
For an organization that has thousands (2Kto 3K CR's per year) of change request, where each CR runs from 15 day to 1 year and they require a project plan for implementation we implemented Single project area with multiple teams ( representing groups by application owners) and a phase plan for each change. This could have been also managed through a seprate Project area per CR, but the complexity of team structure (Team area maintenance) and admin overheads, we had to limit it to single project area.
In another organization (product development) we created a seprate project for each product and its variants and even kept one project per RTC instance to avoid performance issues . The consideration here was large number of SCM streams and components and number of users and size of SCM artifacts, access control requirements.
In my understating the decision would depend on
1. Dependency of project on each other
2. number/ volume of artifacts (SCM / Workitems)
3. number of plans - Project team structure
4. Access Control