Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
EDIT 10/25/2013: Added the step to add git to the Process Template
In TFS 2013 we have added the portfolio backlogs to manage the work one level above the product backlog. The shipped templates contain one portfolio level called the Feature backlog, but you can customize what shows up in the portfolio following the article “Add a backlog to Agile portfolio management”. This blog post describes the differences between the 2012 version of the process templates and the 2013 version and how you can upgrade your custom template. If your current version of TFS is 2012 RTM or 2012 Update 1, you might want to first follow the steps to upgrade your team project to 2012 Update 2.
If you are interested to upgrade your team project, you can use these steps, but it is much easier to use the Configure Feature wizard.
In this release we have made these changes to the process templates:
To get a local copy of the files used in this post, download the process template that matches your process templates best to your local disk. This post assumes the downloaded process template is stored in the local folder “c:\pt\shipped”. Also the blog post assumes the location of your custom process template is stored at “c:\pt\custom”.
Note: if you want to update a process template that was shipped before VS 2012, you need to use the security group Builders instead of Build Administrators.
Now that you have updated your process template, you want to upload it to the collection.
Thanks Ewald, this will be invaluable when the time comes to upgrade :)