Unanswered Left and Right Source Same Team Project for WIT Migration

  • Wednesday, March 21, 2012 8:59 PM
     
     

    Hi all,

    Is it possible with TFS Integration Tools to use the same Team Project for both sides (left and right source) of the migration and map all work items to a newly imported project template work item?

    I need to be able to change a single Team Project from CMMI 4.2 to MS Scrum 1.0 and preserve existing work item data by mapping that data to the new Scrum work item all without creating a new Team Project.

    Thanks in advance,

    Tim

All Replies

  • Thursday, March 22, 2012 2:44 PM
    Moderator
     
     

    Technically, yes.  I really wouldn't advise it though.  It is going to be easy to make a mess of things and it is going to be hard to recover.  Have you considered creating a new team project with the template that you want and then simply branching source into that new team project?  That approach would at least give you a strategy where you could experiment by creating/deleting new team projects until you are happy with the state of the migration and the amount of time it will take. 

    Bill

     
  • Friday, March 23, 2012 4:15 AM
    Owner
     
     

    Thanks Bill for your kindly help.

    Hello Tim,

    I am trying to better understand your issue, please correct me if my understanding is incorrect:

    In your scenario, you would like frist to change a team project from CMMI 4.2 to Scrum 1.0 template, and then migrate the work items created with the CMMI 4.2 template to Scrum 1.0 team project.

    If my understanding is correct, I am sorry to say that as far as I know you are not allowed to dynamically change the team project template for a team project once you have already created it. You need to either create another new team project to use the new process template or to modify the team project to include the new template. See: http://msdn.microsoft.com/en-us/library/ms194914(VS.90).aspx 

    And I personally recommended to create one new team project with the Scrum 1.0 template and then use the TFS Integration tool to migrate work items from CMMI project to Scrum project.

    Thanks.


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us

  • Friday, March 23, 2012 3:40 PM
     
     

    Thank you Bill and Vicky.

    Vicky,

    Yes.  I am trying to figure out if what you have stated is plausible.  I was hoping that even though the Work Item templates have been updated on the Team Project that the raw data was still accessible to TFS Integration Tools so that you could still map old Work Item data to the new fields on the new Work Item template provided by Scrum 1.0 within a single Team Project.

    Thanks,

    Tim

  • Tuesday, March 27, 2012 7:52 AM
    Owner
     
     

    Hello Tim,

    First, in my opinion that all the work items of a specific work item type should be accessiable in the TFS Integration Tool even though there are some modifications of the work item type template.

    Second, just as I mentioned above, I do not think it is possible for you to dynamically change a CMMI team project to a Scrum one.

    So I do not think you can achieve your requirement.

    Thanks.


    Vicky Song [MSFT]
    MSDN Community Support | Feedback to us

  • Friday, March 30, 2012 9:14 PM
     
     

    Vicky,

    It is true that I can't modify the entire process template and I was considering just modifying the categories and work items.  I am just trying to find an ideal situation when there appears to be none.  I could just create source dependencies to the old project but what happens with MS Scrum 2.0 comes out?  I then have to create a third Team Project to account for any new source that is put in the second Team Project that also has code branched from the first team project.  Now I have a continous stream of new Team Projects that have to be created to account for any changes as time progresses and then have to be diligent with co-workers not getting heavy-handed and deleting old Team Projects that they believe are no longer in use.

    Being able to migrate source while retaining version control would just make life so much easier. :)

    Thank you for your suggestions (Bob and Vicky),

    Tim