{"id":13245,"date":"2017-07-02T19:54:00","date_gmt":"2017-07-02T19:54:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/premier_developer\/?p=13245"},"modified":"2019-02-14T20:23:35","modified_gmt":"2019-02-15T03:23:35","slug":"closing-the-gap-between-tfs-and-scrum","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/premier-developer\/closing-the-gap-between-tfs-and-scrum\/","title":{"rendered":"Closing the gap between TFS and Scrum"},"content":{"rendered":"

This post is provided by Senior App Dev Manager, Alexei Govorine<\/a> who covers the use of scrum with TFS and spotlights TFS Version Control, Dashboards, and Markdown.<\/p>\n

\n

Introduction<\/h2>\n

Scrum is one of the most used agile frameworks that helps people address complex problems while delivering products of the highest possible value. For additional information on what Scrum is all about, see the Scrum Guide<\/a>.<\/p>\n

Team Foundation Server (TFS<\/a>) or its online version, Visual Studio Team Services (VSTS<\/a>), are ALM tools created by Microsoft. TFS provides source code management, reporting, requirements management, project management, build automation, release management, and many other features that help teams create high quality software.<\/p>\n

Problem Statement<\/h2>\n

Out of box TFS provides support of Scrum by leveraging a Scrum process template<\/a>. The template was designed according to guidance from the Scrum Guide and there are numerous resources describing how to use Scrum with TFS<\/a>, like Sprint Planning, \u201cSprinting\u201d, and getting visibility into development activities by using TFS Work-items, backlogs, and boards. Unfortunately, there is no clear guidance on how to capture things like: Team Agreements, Definition of Done, Sprint Goals, Sprint Retrospective results\\commitments.<\/p>\n

This article is going to provide a guidance on how to close this gap by leveraging TFS Version Control, Dashboards, and Markdown.<\/p>\n

Solution<\/h2>\n

Using Markdown<\/a> concepts is a great way to extend TFS functionality to bring additional transparency into how the team operates. With every new TFS project a README.md file is created, the purpose of the file is to provide readers with key information about the project, it\u2019s purpose, and objectives. Teams can it use to capture the basic information like: scrum rules (link to scrum guide), link to description of TFS scrum process template, team agreement, and other relevant information.<\/p>\n

Capturing Team Agreement:<\/h3>\n

The team can start by editing the README.md file from the Welcome tab of the project or in VSTS from the landing page of a project.<\/p>\n

1. Click on Edit<\/b> option.<\/p>\n

\"team1\"<\/a><\/font><\/p>\n

Figure 1, Edit README.MD file<\/font><\/p>\n

2. While in the edit mode, the team can capture information about team development process (Scrum), links to tutorials, Team Agreement, and other information that the team finds relevant.<\/p>\n

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

Figure 2, Filling README.MD file with scrum information<\/font><\/p>\n

For the syntax on how to use markdown, see Visual Studio documentation<\/a>. In the example above we used:<\/p>\n