Recently I’ve been working with a customer on migrating their existing Team Project to a new Process Template on Team Foundation Server 2012.
We’ve decided to go with the TFS Integration Tools to move selected Work Items and code across to a new project in a new Team Project Collection. There were a number of alternative options open to us but this is a large project that has been migrated through the versions of TFS and we’re going to take the opportunity to clean it up and consolidate.
I spent some time mapping their existing Microsoft Solutions Framework for Agile Software Development 6.1 project to Microsoft Visual Studio Scrum 2.2. I had to take into consideration some custom fields that had been added to the template and also some legacy fields that had been left hanging around after previous migrations.
The customer is not a heavy Visual Studio user, doing most of the development through Eclipse and as a result they are licensed for Visual Studio Professional 2012. In turn this means that their developers have “Standard” licenses for Team Web Access.
As part of the work we have been doing to transform their development process we have a need to use both the Product Backlog view and the Kanban board, both of which are only available to users who are “Full” licensed users of TWA.
The cost of upgrading the developers to Visual Studio Premium was prohibitive as they will not make use of the additional Visual Studio features and the current Microsoft licensing did not give us any other option.
I evaluated both Urban Turtle and the Eylean products and although they both have their plus points and are very economically priced, neither gave us exactly what we were looking for.
Last week at the Build Windows Conference, Microsoft released a Preview of Team Foundation Server 2013 which also has a Go-Live license.
Ordinarily it would be a pretty gung-ho decision to move your business onto pre-release software but in this case it is worth considering. The reason is that Microsoft have listened to the feedback and re-jigged the licensing for TWA.
TFS2013 now provides both the Kanban Board and the Backlog & Sprint Planning Tools to “Standard” users (VS Pro) and rightfully provides some very cool additional features (Portfolio Management, Team Rooms, Test Case Management, Feedback Management) to “Full” users (VS Premium, Ultimate & Test Pro)
TFS 2012 Team Web Access Levels
TFS 2013 Preview Team Web Access Levels
As a result, there is a strong case to move the project to TFS2013 and although the decision on which way to go has not been made yet, I was worried that the TFS Integration Tools mapping that I had written would need a lot of work to update it for the Microsoft Visual Studio Scrum 3.0 Template.
I downloaded the Scrum 2.2 and Scrum 3.0 Templates and performed a Diff on the folders.
There were some minor build changes and some changes to allow for the new Git support but I was particularly interested in the Work Item and Reporting changes.
Release Burndown report – Order by Iteration Path
Minor change but hopefully a helpful one as I have run into this problem before and presumably this small change to the rdl file will resolve it.
New Category – Feature Category
New Work Item Type - Feature
Both of these have been added to support the new portfolio management functionality in TWA.
And that’s it, so there are no field changes to the core Work Items. Obviously it is still a Preview version of the template but it shouldn’t change significantly and I can make any tweaks if it does.
If you’re in a similar position in that you would like some of the “Full” features from TWA 2012 but the Premium upgrade does not make financial sense then TFS 2013 could give you what you need.