Change Project from Eclipse Way Process to Scrum Process
![]()
Hi,
We are on RTC v2.0.0.2, iFix2 and our projects here were created as "Eclipse Way" processes. We would like to change some of these projects to the "Scrum" Process. I have looked here on the forum for information about this and I found 2 discussions related to this subject. This is the first one: http://jazz.net/forums/viewtopic.php?t=1408&highlight=migrate+scrum The link above appears to say that doing this is possible. After reading it, my understanding is that you could "delete" an existing process template for a project and replace it with a different one. That is, delete the existing "Eclipse Way" XML file and replace it with the "Scrum" process XML file. My first question regarding that would be: "What happens to all of the existing Work Items that were created while the project was using the Eclipse Way process?" This link below here recommends not changing an existing project from an "Eclipse Way" process to the "Scrum" process and instead create a new project from scratch. That may not be practical for some of our larger, mature projects. http://jazz.net/forums/viewtopic.php?t=7772&highlight=migrate+scrum Has anyone here migrated a project created using the Eclipse Way process to the Scrum process? Any thoughts and/or insights would be greatly appreciated. Thanks, -Walter |
One answer
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 06 '10, 5:31 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I believe by the "process template" of a project, you are referring to
the "process configuration source" of the project area. I'll defer the question of the conversion cost to the process experts, but I would think you'd get a variety of dangling process references from work items, as well as report problems when the reports went looking for data that wasn't there in the old work items. Cheers, Geoff On 7/6/2010 5:07 PM, wmansur wrote: Hi, |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.