RTC project organisation

Hello,

I'm deploying RTC. Actually developers work on several hardware and software project and user push request for evolution or bugs reports by word document. Then devloppers add new functionnality or treat bug report. The process is not automized and it's difficult to know if a request is treat or not , how many time leave before a modification, sometime user doesn't really know which softawre and version is concerned because they have not a standard list, etc....

So RTC seems to be a good solution!!

As i have not experience on RTC i have any questions to clarify the organisation of RTC projects and best practice on RTC in general. What is the best solution:

• Create only one RTC project with chronologies or iterations for each developpement (each software project). So project manager will move request from a backlog plan to corresponding iteration's project.
• Create a project for each software developpement (more than twenty projects) . And as all sofwares have interface each other , request on a software would have impact on another project. Is it possible to rely workitem between deferent rtc project? Is it possible to move workitem from a RTC project to another?
• Have a mix ?? In fact developpers work on several software perlaps it's a good idea to have a RTC project by software family?

Thanks for your help,

Thomas