designing RTC project areas for large organizations?
For a large organization that has teams doing both agile and waterfall processes, how do you decide how many RTC project areas to create to make sure that performance is decent and future growth both in number of users and number of artifacts can be handled?
|
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 jeff thomas selected this answer as the correct answer
|
One other answer
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.