This book is your guide to mastering the comprehensive reports that are part of Team Foundation Server and Microsoft's main Application Life Cycle Management (ALM) suite. TFS Reporting provides the ability to track different metrics of development projects throughout the Application Life Cycle; these include team progress, bugs, the current backlog, test progress, and so on, using well-integrated and familiar tools such as Excel and SQL Server Reporting Services. Team Web Access reports are also explained in this book, providing a quick progress status view via different charts, work item queries, as well as inbuilt reports. The book starts by giving you a walkthrough of TFS and the reporting architecture. Then it jumps into the basics of Excel reporting, describing each of the standard reports available. Finally, you will learn how to use the powerful tools available in SQL Server Reporting Services to create and customize robust reports and how to design and customize a dashboard featuring reports relevant to you.

What this book covers

Chapter 1, Team Foundation Server Primer, teaches the basics of the TFS architecture and reporting, and the importance of Application Life Cycle Management.

Chapter 2, Work Item Querying, explains the team project scenario in TFS walks through the types of work item query that results the required work items to know the status of work progress.

Chapter 3, Excel Reporting, explains the basics of integrating SharePoint 2013 with TFS 2013. This chapter also explores Excel report types and how to customize them as required need on different types of dashboards.

Chapter 4, SQL Server Reporting, walks through creating basic SQL reports using Report Builder and Report Designer.

Chapter 5, Team Web Access Reporting, explains Team Web Access levels and their various features (as required) and walks through a very light feature called work item charting. Also, it describes inbuilt standard reports.

What you need for this book

In order to understand the reporting functionalities for TFS 2013, you should have the following set up on the server:

  • TFS 2013 to implement reports

  • The sample Team project in TFS to base reports on

  • SharePoint Server 2013, to integrate TFS with SharePoint for Excel reporting

  • SQL Database 2012 or 2014 to store TFS and SharePoint databases

  • Configuration of the Reporting and Analysis service in SQL Server for SQL reports

Who this book is for

This book is intended for developers, testers, architects, project managers, and for people who want to explore and make use of the reporting facilities of Team Foundation Server 2013 (TFS 2013). The primary audience is anyone working with software development at various cycles using TFS 2013 to administer the project team, source code, builds, work items, and test process. Although no previous experience of reporting is required, a basic understanding of Team Foundation components and project templates will be a plus.


In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.

Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "At runtime, the .rdlc files are processed locally, while the .rdl files are processed remotely."

A block of code is set as follows:

SELECT  DimPerson.Name,
FROM    FactCurrentWorkItem INNER JOIN

New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Clicking the Next button moves you to the next screen."


Warnings or important notes appear in a box like this.


Tips and tricks appear like this.

Reader feedback

Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.

To send us general feedback, simply send an e-mail to , and mention the book title via the subject of your message.

If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on

Customer support

Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.

Downloading the color images of this book

We also provide you with a PDF file that has color images of the screenshots/diagrams used in this book. The color images will help you better understand the changes in the output. You can download this file from:


Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from


Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.

Please contact us at with a link to the suspected pirated material.

We appreciate your help in protecting our authors, and our ability to bring you valuable content.


You can contact us at if you are having a problem with any aspect of the book, and we will do our best to address it.