TFS Team Project Consolidation

1. Utilizing TFS Integration Tools
Jeff Przylucki
Senior Consultant
Polaris Solutions

2. Platinum
Sponsors
Gold
Sponsors
Silver Sponsors

3. Conference Mobile App
• dodn14.azurewebsites.net
• Quick access to conference info
• Build your custom agenda
• Anonymously rate the sessions you attended
• Share with the Twitter-verse

4. •Taking your current TFS Team Project Structure
and migrating content
• Migrate Work Items
• Migrate Source Code
• History or no history?
•Re-organizing you Team Project structure

5. TF Server
Project
Collection 1
Team Project
1a
Team 1A
Team Project
2a
Team Project
3a
Roll-up team
Sub-Team 1 Sub-Team 2
Project
Collection 2
Team Project
A
Team A
Team Project
B
Team Project
C
Team Project
D
Web Team Mobile Team

6. • Over time, TFS tooling has changed
• Agile planning tools
•Teams
• Portfolio level work items (Feature)
• Over time, Your Processes may have changed
•You may just not be happy or satisfied with how
things are currently running in your TFS

8. • Role up all your teams under one Team Project
• Out-of-the-box ability to see Backlogs at every
level
• Maintenance – single Team Project to make
changes against/customize against/Upgrade
• Consistency across your teams

9. • You can’t standardize your Template across all
teams
•Very Large organizations
• Different Divisions or Departments within your
organization

10. • Plan Plan Plan
• Analyze your current Team Projects
• Analyze their current Templates
• Determine What needs to migrated
• Determine Target Template
• Customize Your Template
• Lay out your team structure

11. • Tfs Integration Platform tool
• Downloaded from Visual Studio Gallery
• https://visualstudiogallery.msdn.microsoft.com/eb77e739-c98c-4e36-
9ead-fa115b27fefe
• Tfs Integration Platform Field Mapping Tool
• Downloaded from CodePlex
• http://tfsintegrationmapper.codeplex.com/

12. • Moves Work Items and Source Control between TFS Servers
• Useful for Migrations/Consolidations
• Provides ability to Map Work Items from one Project to Another
• XML Based Mapping
• Map Fields to Fields
• Lets you map values from one to another
• Aggregate fields to combine fields to get the value of the new item

13. • Generates the Mapping XML For you
• Pick two Work Item Type Definitions, and map field to field!

14. <FieldMap name="UserStoryToProductBacklogItemFieldMap">
<MappedFields>
<MappedField MapFromSide="Left" LeftName="System.AssignedTo" RightName="System.AssignedTo" />
<MappedField MapFromSide="Left" LeftName="Microsoft.VSTS.Common.ClosedDate" RightName="Microsoft.VSTS.Common.ClosedDate" />
<MappedField MapFromSide="Left" LeftName="System.Description" RightName="System.Description" />
<MappedField MapFromSide="Left" LeftName="System.History" RightName="System.History" />
<MappedField MapFromSide="Left" LeftName="Microsoft.VSTS.Build.IntegrationBuild" RightName="Microsoft.VSTS.Build.IntegrationBuild" />
<MappedField MapFromSide="Left" LeftName="System.Reason" RightName="System.Reason" />
<MappedField MapFromSide="Left" LeftName="System.State" RightName="System.State" valueMap="UserStoryStateMap" />
<MappedField MapFromSide="Left" LeftName="System.Title" RightName="System.Title" />
<MappedField MapFromSide="Left" LeftName="Microsoft.VSTS.Scheduling.StoryPoints" RightName="Microsoft.VSTS.Scheduling.Effort" />
</MappedFields>
<AggregatedFields>
<FieldsAggregationGroup MapFromSide="Left" TargetFieldName="System.IterationPath" Format="{0}{1}">
<SourceField Index="0" SourceFieldName="System.TeamProject"></SourceField>
<SourceField Index="1" SourceFieldName="System.IterationPath"></SourceField>
</FieldsAggregationGroup>
<FieldsAggregationGroup MapFromSide="Left" TargetFieldName="System.AreaPath" Format="{0}{1}">
<SourceField Index="0" SourceFieldName="System.TeamProject"></SourceField>
<SourceField Index="1" SourceFieldName="System.AreaPath"></SourceField>
</FieldsAggregationGroup>
</AggregatedFields>
</FieldMap>

15. I have two Team Projects in one collection
one is a Scrum 3
one is an Agile v7
I am going to migrate those two Team Projects to a single, new Scrum
2013.3 Team project in a new collection.

16. Jeff Przylucki
Senior Consultant @ Polaris
Solutions
Microsoft ALM MCSD
Jeff.Przylucki@PolarisSolutions.com
http://blog.oneluckidev.com