Hello everybody, this is my first post in those forums, so please forgive me if I'm breaking any rules here..

Our team considering to move to RTC for source control, defect management and, maybe, project progress tracking. The team is something like 60 developers and testers, all around the globe. Process that is currently used is a classic waterfall, there are no thoughts to move to Agile in near future. Currently sources and defects are managed in CMVC, builds are managed through Build Forge.

Do you think moving to RTC is the right choice for us ? Shall we use it for all our needs, or should we consider connecting it with Rational Quality Manager for managing defects and Rational Clear Case for managing sources ? Can we stay with BuildForge or should we consider using built-in abilities of RTC for builds ?

Hi Michael

Welcome to the forum.

Given your description, you could use RTC for a lot of your work.

Decide what your priorities are - and starting using RTC for that aspect first. Definitely keep Buildforge - this will plug in to the builds in RTC and will keep a lot of your hard work on the build scripts.

You can use RTC for defects too (see how it is used here on jazz.net) - but if you have a separate quality team and a lot of UI/performance test automation - you might want to look at Quality Manager.

Hope that gives you some ideas - and please keep asking questions as they occur to you.

anthony

Being a classic waterfall project is fine ... agile support is there if
you need it, but a waterfall process is handled equally well by RTC.

WRT BuildForge, the Jazz Build component is integrated with BuildForge,
so you can just keep your BuildForge builds (note: that integration has
been significantly improved for RTC-3.0).

Rational Quality Manager helps you manage your testing efforts (it has
the RTC work item component built in for defect management, but you can
use any OSLC CM compliant repository for defect management in RQM). So
you can start with RTC, and then add in RQM as you need it (in RTC-3.0,
RTC and RQM can share a single server, so it is even easier to
incrementally start using RQM functionality).

Similarly, if you find that you need the advanced SCM features of
ClearCase, you can add ClearCase in to your environment, and use the
ClearCase Bridge to link your ClearCase work into the RTC work items,
planning, etc.

Cheers,
Geoff

On 8/24/2010 5:38 AM, mishka wrote:

Hello everybody, this is my first post in those forums, so please
forgive me if I'm breaking any rules here..

Our team considering to move to RTC for source control, defect
management and, maybe, project progress tracking. The team is
something like 60 developers and testers, all around the globe.
Process that is currently used is a classic waterfall, there are no
thoughts to move to Agile in near future. Currently sources and
defects are managed in CMVC, builds are managed through Build Forge.

Do you think moving to RTC is the right choice for us ? Shall we use
it for all our needs, or should we consider connecting it with
Rational Quality Manager for managing defects and Rational Clear Case
for managing sources ? Can we stay with BuildForge or should we
consider using built-in abilities of RTC for builds ?