I would recommend not trying to convert your existing project areas from
Eclipse Way to Scrum, but rather create a new project area based on the
current Scrum template.

Once you have done so, the easy thing to do first is to just change the
ownership of your streams, components, build definitions, and build
engines to be the new project area.

Leave your old plans in the old project area. I'd also leave all
resolved work items in the old project area.

Create the appropriate team areas, timelines, iterations, categories,
and map the categories to the appropriate team areas.

And finally for the only non-trivial part: move the unresolved work
items that you still care about to the new project area. RTC will do
its best to fix-up the work-item fields that need to be changed, but you
probably will want to quickly review the result, and manually fix-up
anything that it didn't guess right on. Note that you currently have to
do this one workitem at a time, although there is some bulk-move
functionality you can "beta test" (see this forum for details).

So that's what I'd do ... RTC component leads, please comment if you
would do any of this differently.

Cheers,
Geoff

viveknair wrote:

viveknairwrote:
Hi,
We recently migrated from RTCV1.0 to 2.0. We had originally set
up our project areas using the "Eclipse Way " process
template. Now, some teams want their project areas to be converted
from Eclipse to Scrum. Is this possible without having any
side-effects? If so , what is the procedure to do so?
Also, could someone point me to any documentation that does a
comparison between the Eclipse and Scrum processes?
Thanks
Vivek

If converting an existing project-area is not possible, is it possible
to create a new project area with the required template and move the
source-control components over to it ? at the same time preserving
the history?