Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Visual Studio Team Services: How to migrate from Agile to Scrum process template

Tags:

I'm using Visual Studio Team Services (previously Team Foundation Service, not Team Foundation Server) and I need to migrate a team project process template from Agile to Scrum.

Doe anyone know how to do it?

like image 306
Carlos Coelho Avatar asked Nov 18 '13 16:11

Carlos Coelho


People also ask

How do I change the project process in Scrum?

Change the project processChoose Projects, and then choose the actions icon for the project you want to change, and select Change process. Here we choose the MyAgile project. Follow the steps in the wizard. Choose the Scrum - Inherited process that you created earlier and then choose Save.

Which process templates are available in Azure DevOps?

The work tracking objects contained within the default processes and process templates—Basic, Agile, CMMI, and Scrum—are the same and summarized below. The Basic process is available from Azure DevOps Server 2019.1 and later versions. For simplicity, they're referred to as a "process."

What is the difference between agile and Scrum in Azure DevOps?

A framework such as Scrum can help an enterprise adopt Agile principles in day-to-day operations. DevOps is a practice that brings development and operations teams together. On the other hand, Agile is an iterative methodology with a strong focus on collaboration, rapid releases, and customer feedback.


1 Answers

There are a couple of different ways to go about this, depending on what you want at the end. Most importantly, there is no way to change the process template from one to the other inside a Team Project, so you'll have to create a new Team Project with the Scrum Template to migrate to.

If you want history & attachments: Then you need to use the TFS Integration Platform. You'll create a xml mapping to flow the work items and source code from one project to the other. There are quite a few issues with going this direction including, history is compressed, the tool is notoriously finicky, shared steps (and other things) don't migrate and more. This is definitely not the recommended option, but sometimes you don't have a choice. Here's where to get the tool: http://visualstudiogallery.msdn.microsoft.com/eb77e739-c98c-4e36-9ead-fa115b27fefe

If don't need history, or can keep the other Team Project around: For this method, moving the code is easy (it's even easier if you've got a Git project, and you'll get history. Use the git-tf functionality to move your source to Git). Just check out from one repository, switch your workspace mapping and check in to the new repository.

To move your work items, use work item queries and export them to Excel. Then copy/paste into a second Excel spreadsheet and upload them to the new Project. This is by far the easiest method. Here's a detailed explanation:

1) From Agile template project: for each work item type that you want to move, create a work item query to pull all the ones you want and export them all to Excel (for example a query to pull all requirements and another for tasks)

2) From the Scrum template project: create a work item query for each work item type that you want to import and export it to Excel. It's going to be blank, but you're going to use this Excel spreadsheet to upload in a minute.

3) Copy/past from one Excel spreadsheet to the other, being careful to NOT copy column headers. A neat trick is to copy the History column from the old project into the Comments field in the new project.

4) Publish the results. Viola, you're migrated.

like image 62
Andrew Clear Avatar answered Oct 20 '22 14:10

Andrew Clear