Why should we move to RTC if we have other non-JAZZ?
Our organization is reviewing the option to move to RTC. Has anyone implemented RTC into an environment with non-JAZZ tools and it has provided them value add to their SDLC? If so, how? We use the Waterfall model for our software development processes.
For source control (over 10+ years of VOBs data), we use UCM ClearCase/ClearQuest. It sounds like RTC would not replace UCM CC/CQ, but will work along side RTC.
The organization has the following tools and will not retire them. We have HP ALM, for Defects and Testing; Serena, for Requirements/Release management; BMC's BRPD and BRPM, for build/deploy automation, BMC Remedy on Demand for Change Management, and HP PPM for managing application enhancements and maintenance requests.
For source control (over 10+ years of VOBs data), we use UCM ClearCase/ClearQuest. It sounds like RTC would not replace UCM CC/CQ, but will work along side RTC.
The organization has the following tools and will not retire them. We have HP ALM, for Defects and Testing; Serena, for Requirements/Release management; BMC's BRPD and BRPM, for build/deploy automation, BMC Remedy on Demand for Change Management, and HP PPM for managing application enhancements and maintenance requests.
Accepted answer
As mentioned, if you're not retiring other tools, then what would be the point?
This is my own opinion, but each of the functional parts of RTC is limited in some way. The Work Item component is ok, the planning is useless unless used with the Work Items and only if you're doing agile, the reporting and scm are fairly weak. However, when you put all these things together, you start to get a fairly useful tool.
So for example, I would never replace ClearCase with RTC scm, however, if you also plan to use Work Items, and maybe agile planning, throw in the dashboard, then you start to get a useful solution.
3 other answers
In our organization we've added RTC to environments to either substitute, replace, or fill a gap. For example, moving out of ClearCase and into the RTC Jazz SCM, or leaving Synergy/Change to use the Jazz SCM/change-management parts of RTC, or to add a change-management/planning layer to base ClearCase.
It sounds like you already have your version control system (UCM ClearCase), your change-management system (UCM ClearQuest), and a basket of non-negotiable tools for various aspects of managing your lifecycle.
If nothing is replaceable, I guess the question is: Where do you think you see RTC fitting-in?
It sounds like you already have your version control system (UCM ClearCase), your change-management system (UCM ClearQuest), and a basket of non-negotiable tools for various aspects of managing your lifecycle.
If nothing is replaceable, I guess the question is: Where do you think you see RTC fitting-in?