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
With the latest Team Foundation Service update and with Visual Studio Team Foundation Server 2013 RTM, we have changed the names of all process templates. From now on, the process template names will reflect the version of Team Foundation Server that supports their download.
The new names are:
You can access process guidance and charts that compare the features of each template here: Work with team project artifacts, choose a process template.
While the names have changes, the major and minor version numbers remain intact. The version numbers support the Configure Features wizard in choosing the latest process template to update a team project after TFS upgrades.
If you customize a team project, you may need to customize the process template to support the upgrade process. In doing so, you may need to update the version numbers. To learn more, see Update a customized process template to access new features.
To learn more about changes introduced with the TFS 2013 process templates, see this blog post:. To access the new WITs and other new tools, you'll need to update an upgraded team project using the Configure Features wizard.
Why aren't the names
•Microsoft Visual Studio Scrum 2013
•Microsoft Visual Studio Agile Software Development 2013
•Microsoft Visual Studio CMMI Software Improvement 2013
•MSF for Scrum 2013
•MSF for Agile Software Development 2013
•MSF for CMMI Software Improvement 2013
Why do you have different naming patterns?
MSF is Microsoft Solutions Framework and not Microsoft. MSF defines Agile and CMMI processes but not Scum.
That is probably the reason for the different names.
I still see different names.
Microsoft Visual Studio Scrum 3.0 (default)
MSF for Agile Software Development 7.0
MSF for CMMI Process Improvement 7.0