{"id":5141,"date":"2010-06-07T05:03:55","date_gmt":"2010-06-07T05:03:55","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/bharry\/2010\/06\/07\/a-scrum-process-template-for-tfs\/"},"modified":"2024-06-25T12:02:26","modified_gmt":"2024-06-25T19:02:26","slug":"a-scrum-process-template-for-tfs","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/bharry\/a-scrum-process-template-for-tfs\/","title":{"rendered":"A Scrum Process Template for TFS"},"content":{"rendered":"

Since TFS 2005, we have delivered two process templates with TFS: MSF Agile and MSF for CMMI.\u00a0 Our goal with MSF Agile was to create a relatively simple process template for teams doing Agile software development.\u00a0 We designed it to enable a wide range of iterative development processes without too much process control.\u00a0 In doing so, it doesn\u2019t match any existing process directly but rather is pretty flexible to adapt to your process.<\/p>\n

Over the past couple of years, Scrum has evolved as an extremely popular iterative development process and we\u2019ve been getting feedback that our Agile template feels unnatural for teams trying to do Scrum.\u00a0 For example, it uses different terminology like Iteration rather than Sprint, User Story rather than \u201cProduct Backlog item\u201d, etc.<\/p>\n

Today we are releasing a Beta of a new TFS process template specifically optimized for Scrum projects \u2013 Team Foundation Server Scrum v1.0 Beta<\/a>.\u00a0 You can also find it on our Process Templates and Tools<\/a> page on MSDN.<\/p>\n

To demonstrate some of the differences between our new Scrum process template and the existing MSF Agile process template, let\u2019s look at the list of work item types in the two templates:<\/p>\n\n\n\n\n\n\n\n\n\n\n
TFS Scrum v1.0 WITs<\/strong><\/td>\nMSF Agile v5.0 WITs<\/strong><\/td>\n<\/tr>\n
Product Backlog Item<\/td>\nUser Story<\/td>\n<\/tr>\n
Bug<\/td>\nBug<\/td>\n<\/tr>\n
Task<\/td>\nTask<\/td>\n<\/tr>\n
Impediment<\/td>\nIssue<\/td>\n<\/tr>\n
Test Case<\/td>\nTest Case<\/td>\n<\/tr>\n
Shared Steps<\/td>\nShared Steps<\/td>\n<\/tr>\n
Sprint<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

As you can see, the new Scrum work item types match the standard Scrum terminology.<\/p>\n

You can also see the difference in the state transition models for the new template:<\/p>\n

Product Backlog Item and Bug Work Items<\/p>\n

\"Image<\/a><\/p>\n

Task Work Item<\/p>\n

\"Image<\/a><\/p>\n

Impediment Work Item<\/p>\n

\"Image<\/a><\/p>\n

Both the states and the terminology are different and match the Scrum process.<\/p>\n

We\u2019ve also built some new reports designed to highlight the key Scrum tracking metrics:<\/p>\n