New Pluralsight course: Team Foundation Server 2015

My latest Pluralsight course titled “End-to-End Software Development with Team Foundation Server 2015” is now available in the Pluralsight library.



This course will take you through the great features available in TFS 2015 to help you and your team plan, code, build, and test your applications.  The course is broken down into the following modules:



Introduce the collaboration features available that will help you and your team succeed delivering software.  We take a look ahead to what you will learn in the course


Understanding the Feature Path from TFS 2013


Covers the major features released since TFS 2013 RTM, focusing on the Agile tools, Git enhancements, charts, and more

Installing and Configuring TFS 2015


Upgrade from TFS 2013 to TFS 2015

Working with new Kanban Board Features


Updates to the Agile functionality in TFS, including Kanban board features.  This module walks you thought Portfolio-level planning, Kanban board customizations, Sprint and capacity planning, charts, and dashboards.

Working With New Version Control Features


Select between using Team Foundation Version Control or Git, or better yet, include both Git and TFVC in the same team project. This module covers enhancement to branching in Visual Studio, rebasing, and Pull Request improvements.

Building Software


TFS 2015 introduced a new build system with a new web-based interface and a much more flexible infrastructure that includes Agents, pools and queues. This module shows you how to configure a build agent, create a build definition, and customize your builds to get the most out of the build system.

Testing Software


When you access the Test Hub in the TFS 2015 web portal, you are able to plan, test, and analyze your team’s testing efforts.   The Test hub in TFS 2015 was enhanced to give you and your team the ability to perform most test-related functions right on the browser. This means, that even if you are testing on a non-Microsoft operating system, you are able to take advantage of these features.  I cover the new Exploratory Testing capabilities included by the Chrome Extension and the ability to create test cases from the Kanban board.

Integrating with TFS 2015


One of the easiest ways to extend TFS functionality is through the Visual Studio Marketplace. The marketplace includes extensions published by Microsoft and third-parties that extend the built-in TFS functionality.   The module shows you how to work with Marketplace extensions, create your own extension, work with the TFS REST API, and integrate with third-party apps through the use of Service Hooks.


I am very proud of this new course and I hope that you enjoy it and it helps you be successful with Team Foundation Server 2015!


You can access my other courses here:

About esteban

Esteban is the Founder and Chief Technologist at Nebbia Technology, an ALM consulting and Azure-powered technology company. He is a software developer with a passion for ALM, TFS, Azure, and software development best practices. Esteban is a Microsoft Visual Studio ALM MVP and ALM Ranger, Pluralsight author, and the president of ONETUG (Orlando .NET User Group).

2 thoughts on “New Pluralsight course: Team Foundation Server 2015

  1. paul

    Hi Esteban,
    I viewed your Pluralsight video on this with emphasis on test manager(which was great). I did have a question on creating test cases from the Kanban board.

    We have customized our test case template to provide hour estimates for testing. The problem is, those hours are not calculated for the burndown chart. A workaround was creating a task with an Activity of test which does count on the burndown but does not seem to be the most efficient process. The test cases also do not show when your viewing the Kanban at the Current iteration level.

    Was wondering if you had any recommendations on this. They seem to be deficiencies on the testing process and I can’t imagine we’re the only company having these workflow issues.

    Thanks and keep up the great content!

    1. esteban

      Paul, thank you for checking our my course.
      The way that you are doing it is the only way to get the sprint burndown to work, since it is based on task progress.
      Keep in mind that a Test Case can be used across multiple suites and plans, which means that your estimate for a test case (and the amount of time it took you to run it) only makes sense in the context of the suite. So tasks are the only way for VSTS and TFS to know time estimates, or at least, that is how the system is built.

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you human? *