TFS 2013.2

OK, this time I am a bit late…. Microsoft released TFS 2013.2 in the beginning of April, it is as the earlier updates cumulative. It’s no big update but it includes a couple of things that makes life easier for the development teams.

Tags in queries

The possibility to Tag a Work Item as been there for some time but it hasn’t been possible to use the Tags in a Work Item Query. This is now possible, the Tag field is now shown with all the other fields in the Query Editor and of course also in the result.

TFS 2013.2.1

Weekends in the Burndown

Since TFS 2012 I and a lot of my customers have been irritated that the weekends are shown in the Burdown chart. You can now finally select our working days, thank you Microsoft!

TFS 2013.2.2

Start date for the Cumulative flow diagram

Another diagram change is that you now can set a start date for the Cumulative flow diagram. The diagram shows User Stories/state over time.

Simple diagrams (Charting)

With Work Item Chart that has been around for some time it has been possible to create diagrams from a Work Item Query, you can for example show who has the most active bugs assigned at the moment. The new thing in Update 2 is that you can pin the chart in the start page, just like a Team Query.

TFS 2013.2.3

Export testplans to HTML

It has earlier been difficult to print the data in the testplans as in a report, now it’s possible to print or email the content in a testplan with test, teststeps, configuration and run settings.

TFS 2013.2.4

Microsoft release cycle.

Microsoft has since TFS 2012 increased the TFS release to about one major and 3-4 minor releases per year. Download TFS 2013 Update 2 here.

Migrating Scrum for Team System 3.x to MS Scrum 2.0

A lot of you have probably used the Scrum for Team System process template from Conchango in previous versions of Team Foundation Server (pre 2012). Scrum for Team System is now an open source project on Codeplex and I haven’t seen any plans to a TFS 2012 versions. For those of you wanting to use the new TFS 2012 features I have two recommendations:

  1. The easiest way is to create a new TFS project and start using it
  2. If you want to upgrade an existing project read my blog below.

Download Work Item type definitions

  1. Download the process template for MS Scrum 2.0 and Scrum for Team System 3.0x with the Process Template Manager for example to C:MyDownloadedTemplates.  If you have modified the Scrum for Team System with fields of your own you should download those instead.

Change Work Items

  1. Identify and copy fields that you use that differ from Scrum for Team System to the MS Scrum Work Item definitions and identify the state changes between the templates. Some of them also include name changes of the Work Item type definition. If you have added fields of your own you should also include them.
Conchango WI MS Scrum WI Field mapping States mapping
Product backlog item Product backlog Item
  •   Business value (Scrum) – Business Value
  •   Storypoints – Effort

 

 

  •   In progress – Comitted
  •   Not Started – New
  •   Deleted- Removed
  •   Descoped-Removed
  •   Broken –  Removed
  •   Depricated – Removed
Sprint backlog task Task
  • Task Priority (Scrum) – Backlog Priority
  • Work Remaining (Scrum) Remaining Work
  •   Task Priority (Scrum) – Backlog Priority
  •   Work Remaining (Scrum) Remaining Work
  •   Not Started – To Do
  •   Deleted – Removed
  •   Descoped – Removed
Bug Bug
  •   Active – New
  •   Ready For Test – Done
  •   Closed – Done
  •   Deleted – Removed
  •   Ignored – Removed
Acceptance test Test Case
  •   Not Implemented – Design
  •   Deleted – Closed
  •   Ready for Test -Ready
  •   Passed – Ready

 

 

Here is what the PBI modification may look like

Here is what the Task modification may look like. Note that I have changed the name of the MS Scrum Task to Sprint Backlog Task so that is will overwrite the existing WI definition, it will be renamed later.

 

Upload Work Item Type definitions

Upload the modified WIs from the MS Scrum template to the project that is to be modified with witadmin.exe.

1. Start a Visual Studio command prompt and run the command below

CD C:MyDownloadedTemplatesMicrosoft Visual Studio Scrum 2.0WorkItem TrackingTypeDefinitions

2. Upload the product backlog Item WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”ProductBacklogItem.xml”

3. Upload the Task WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”Task.xml”

4. Change name of the WI from Sprint Backlog Task to Task

witadmin renamewitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject”  /n:”Sprint Backlog Task” /new:”Task”

5. Upload the Bug WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”Bug.xml”

6. Upload the TestCase WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”TestCase.xml”

7. Change name of the WI from Acceptance Test to Test Case

witadmin renamewitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject”  /n:”Acceptance Test” /new:”Test Case”

8. Upload the Impediment WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”Impediment.xml”

9. Upload the Shared step WI

witadmin importwitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /f:”SharedStep.xml”

Copy fields using excel

Use Excel to copy fields between the old and the new fields that differs. Also use Excel to change the stare model.

Remove WIs that are not used.

The following WIs are not used in the MS Scrum template, remove them.

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Sprint Retrospective”

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Release”

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Sprint”

witadmin destroywitd /collection:http://MYTFSSERVER:8080/tfs/MyCollection /p:”MyProject” /n:”Team Sprint”

 

Work Item Queries

1. Create a new WIq folder called Old and move all old Queries there

2. Copy WIQs from a project  Created with MS Scrum with copy-paste

3. Modify queries under the Current Sprint folder to match your sprints

 

Change sharepoint

You may not be able to access the SharePoint site because old web parts might be missing, to fix this follow these steps.

  1. Go to Site settings, http://MyTFSserver/sites/MyCollection/MyProject/_layouts/settings.aspx
  2. Activate sites features Scrum Dashboards with reporting and Team Collaboration Lists
  3. Go to http://MyTFSserver/sites/MyCollection/MyProject/Dashboards/Forms/AllItems.aspx
  4. Select ”Open with  Windows Explorer”
  5. Copy Release.aspx and overwrite Default.aspx
  6. Go to Site settings, choose ”Title, Description and Icon”
  7. Change the Icon URLto /_layouts/Microsoft.TeamFoundation/images/tfstitlegraphic.gif
  8. Click update the user interface

 

 

Add new reports

  1. Remove the old reports
  2. If you haven’t installed Team Foundation Power Tools, install it.
  3. Run tfpt addprojectreports to add the new reports

tfpt addprojectreports /collection:http://MYTFSSERVER:8080/tfs/MyCollection /teamproject:”MyProject” /processtemplate:”Microsoft Visual Studio Scrum 2.0″ /force

 

Add TFS 2012 functionality

1. Start TFS Web access for the project

2. Click Backlog

3. Click Configure

4. Click Verify

5. Click Configure

6. Click Close

 

You now have I migrated project with a new process template. Next step is to set dates to your Iterations and add members to your team!

Nyheterna i Visual Studio 2012 ALM (Swe)

Jag och min kollega Mathias Olausson har blivit intervjuade av Dag König på Microsoft, ämnet är nyheterna i Visual Studio 2012 ALM, lyssna på Podcasten här.

Some features of Team Web Access are not visible to you

The first time you log in to TFS Web Access after installing TFS 2012 you might get the message “Some features of Team Web Access are not visible to you”. If you click show details you will see “In order to use all the features of Team Web Access, you must have the correct license and configuration. For more information”

To add users to the correct group first click “Administer Server”

Then click “Control Panel”, “Web Access” and “Limited”, “Full” or “Standard” depending on the group you want to add your users/AD-groups to.

  • Limited:
    • This level of access restricts the user so that they can only view work items that they create in Team Web Access (also known as Work Item Only View). No other features, such as team pages, are available to users in this group. For more information, see Manage Work Items in Work Item Only View (Team Web Access).
    • No client access license (CAL) is required for this level of Team Web Access.
  • Standard:
    • This is the default level of access in Team Web Access for your users. Members of this group can view all Team Web Access features except for:
      • sprint planning and backlog views
      • any of the features for requesting feedback from users and managing that feedback
    • A Team Foundation Server (TFS) CAL is required for all users with this level.
  • Full:
    • This level is reserved for users who are licensed to use all features available in Team Web Access, including the sprint planning and backlog management tools and the Request and Manage Feedback tools.
    • To use these features, your user must be licensed for one of the following MSDN subscriptions: Visual Studio Test Professional with MSDN, Visual Studio Premium with MSDN, or Visual Studio Ultimate with MSDN. These MSDN subscriptions each include a TFS CAL for the subscriber.

Read More in MSDN