Setup of Project Areas
Hi!
We have decided to switch from clearcase clearquest (ucm) to ibm jazz (rtc, rqm, dng).
Now I have to plan the migration the configuration and the setup.
We are much more product instead of project driven. We have a hierarchical structure of our components.
customer systems use products
products use product components
product components use components
in clearcase is no really difference, but in clearquest we created a record type "System" which has different mandatory fields for planning purposes (depending on which hierarchical component is choosen).
my question is, how can we setup project areas the best way (for planning and also for component reuse)?
We also plan to use configurations!
Thank you!
Regards Gerald
We have decided to switch from clearcase clearquest (ucm) to ibm jazz (rtc, rqm, dng).
Now I have to plan the migration the configuration and the setup.
We are much more product instead of project driven. We have a hierarchical structure of our components.
customer systems use products
products use product components
product components use components
in clearcase is no really difference, but in clearquest we created a record type "System" which has different mandatory fields for planning purposes (depending on which hierarchical component is choosen).
my question is, how can we setup project areas the best way (for planning and also for component reuse)?
We also plan to use configurations!
Thank you!
Regards Gerald
One answer
Hi Gerald,
In RTC there is no option to display different attributes depending on the enumeration. So either you can select couple of different work item types or specify which fields are required depending on attribute value.
The project areas and team areas in RTC are designed to set the scope of visibility so it is up to you how you want to manage mapping project area -> system/product. There is also option to share project area template so you could potentially have the same work item types in different project areas.
Regarding planning: RTC enables to create cross project plans so there would not be an issue with having many project areas.
It all depends what is the mappings between customer systems, products and components. If it is one to many, then you can have many project areas. Otherwise it could be difficult to be manageable.
Let me know if that helps.
In RTC there is no option to display different attributes depending on the enumeration. So either you can select couple of different work item types or specify which fields are required depending on attribute value.
The project areas and team areas in RTC are designed to set the scope of visibility so it is up to you how you want to manage mapping project area -> system/product. There is also option to share project area template so you could potentially have the same work item types in different project areas.
Regarding planning: RTC enables to create cross project plans so there would not be an issue with having many project areas.
It all depends what is the mappings between customer systems, products and components. If it is one to many, then you can have many project areas. Otherwise it could be difficult to be manageable.
Let me know if that helps.
Comments