Geek Answers Handbook

How to convert MSF Agile to Scrum 2.0

I just migrated from TFS 2010 to TFS 2012 RC.

I also upgraded my team projects to MSF Agile 6 with the built-in upgrade function, but I would like to use the SCRUM template instead of using MSF Agile.

I have not found a way to achieve this.

Do you have any ideas on how to do this, or am I following the MSF Agile process?

+4
source share
2 answers

You can completely switch from one process template to another.

I have detailed 7 ways to achieve this with all the pros and cons of a blog:

Now you, I think, look at # 7 as moving in place with MSF Agile to the Visual Studio Scrum Template. If you follow the instructions for # 7 by renaming work items and importing new ones, then you should be good. I do this for the client today, and I have done this several times, and it works well.

Depending on how you decide to do this, there is some data loss. You cannot get away from it, no matter what you do, but it minimizes this loss and allows you to completely switch to a new process template. Make sure you add all the fields that do not exist in the old template, and you can then rename these old fields with some kind of tag so you can find them later ...

Here is the clean (and latest) Agile (any version) for the Visual Studio 2.0 script. Make sure you read blog posts and determine what you are trying to achieve with each step.

SET TP="Mt=yTeamProject" SET COLLECTION="http://myTFSServer:8080/tfs/myCollection" SET PTROOT=C:\temp\Microsoft Visual Studio Scrum 2.0 witadmin listwitd /collection:%COLLECTION% /p:%TP% witadmin renamewitd /collection:%COLLECTION% /p:%TP% /n:"User Story" /new:"Product Backlog Item" witadmin renamewitd /collection:%COLLECTION% /p:%TP% /n:"Issue" /new:"Impediment" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\Bug.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\CodeReviewRequest.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\CodeReviewResponse.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\FeedbackRequest.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\FeedbackResponse.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\Impediment.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\SharedStep.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\ProductBacklogItem.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\Task.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\ProductBacklogItem.xml" witadmin importwitd /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\TypeDefinitions\TestCase.xml" witadmin importcategories /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\Categories.xml" witadmin importcommonprocessconfig /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\Process\CommonConfiguration.xml" witadmin importagileprocessconfig /collection:%COLLECTION% /p:%TP% /f:"%PTROOT%\WorkItem Tracking\Process\AgileConfiguration.xml" tfpt addprojectreports /collection:%COLLECTION% /teamproject:%TP% /processtemplate:"Visual Studio Scrum 2.0"

This script is used at your own risk and should only be used against the test server, until you make sure that you have a workflow.

There is also a built-in function in 2012 and 2013 to “enable new features” that introduces what is needed to create a process template.

+10
source

This is possible with the TFS Integration Toolkit . Please look at the SO stream for more information.

-1
source

More articles:


All Articles