Team Foundation Server
Overview
Randy Pagels
Developer Technology Specialist
Developer Platform & Evangelism | Heartland District
Microsoft Corporation | Detroit, MI
Project Visibility
Streamline the Process
REPORTING CAPABILITIES
Reporting Structure
Configuration DB
Collection 1
Team Project X
Team Project Y
Collection 2
Team Project X
Team Project Y
Collection 3
Team Project X
Team Project Y
Data Warehouse
Relational Warehouse
Analysis Services Cube
Visualizing the Cube
Task
Test Case
Bug
Active
Resolved
Closed
Ready
Work Items
User Story
State
Streamline the Process
EXCEL REPORTS
Simplified Reporting
• Reports using SQL
Server Reporting
Services
• Detailed and thorough
• Workbook queries
with Microsoft
Office Excel
• Fast and flexible
Excel Reporting
• Included Excel Reports
– Project Management
– Bug Backlog Management
– Build Management
– Test Management
• Excel Report Generation
Excel Reports - Project Management
• Burndown
• Task Progress
• User Story
Progress
• Issue Trends
Excel Reports – Bug Backlog Management
Bug Progress
Bug Trends
Bugs by Priority
Bugs by
Assignment
• Bug Reactivations
•
•
•
•
Excel Reports – Build Management
• Code Coverage
• Code Churn
• Build Status
Excel Reports – Test Management
•
•
•
•
•
Test Plan Progress
Test Case Readiness
User Story Test Status
Test Activity
Failure Analysis
Excel Report Generation
• Create directly from Work Item query
• Generates
– Table of contents
– PivotTable & PivotChart reports
• Report options
– Current reports
– Trend reports
Excel Report Generation
• Current
– Work Item Count
• Work item Type
• Assigned To
• State
• Trend
– Work Item Count
• Work Item Type
• Assigned To
• State
Streamline the Process
SQL SERVER REPORTING SERVICES
TFS Reporting Experience
SQL REPORTING SERVICES REPORTS
Reports Available Based on Process Template
Agile & CMMI
• Bugs
• Bug Status
• Bug Trends
• Reactivations
• Builds
• Build Quality Indicators
• Build Success Over Time
• Build Summary
• Project Management
• Burndown and Burn Rate
• Remaining Work
• Status on All Iterations
• Unplanned Work
• Tests
• Test Case Readiness
• Test Plan Progress
Agile
• Project Management
• Stories Overview
• Stories Progress
CMMI
• Project Management
• Requirements Progress
• Requirements Overview
Scrum
• Release Burndown
• Sprint Burndown
• Velocity
Bug Status Report
•
•
•
•
Is the team fixing bugs
quickly enough to finish on
time?
Is the team fixing high
priority bugs first?
What is the distribution of
bugs by priority and severity?
How many bugs are assigned
to each team member?
Bug Trends Report
•
•
•
How many bugs is the team
reporting, resolving, and
closing per day?
What is the overall trend at
which the team is processing
bugs?
Are bug activation and
resolution rates declining
toward the end of the
iteration as expected?
Reactivations Report
•
•
•
How many bugs are being
reactivated?
How many user stories are
being reactivated?
Is the team resolving and
closing reactivated bugs at
an acceptable rate?
Build Quality Indicators Report
•
•
•
What is the quality of the
software?
How often are tests passing,
and how much of the code is
being tested?
Based on the code and test
metrics, is the team likely to
meet target goals?
Build Success Over Time Report
•
•
•
What parts of the project have produced software that is ready to be tested?
What parts of the project are having trouble with regressions or bad checkins?
How well is the team testing the code?
Build Summary Report
•
•
•
•
•
What is the status of all builds over time?
Which builds succeeded?
Which builds have a significant number of changes to the code?
How much of the code was executed by the tests?
Which builds are ready to install?
Burndown and Burn Rate Report
•
•
•
Is the team likely to finish the
iteration on time?
Will the team complete the
required work, based on the
current burn rate?
How much work does each
team member have?
Remaining Work Report
•
•
•
•
•
What is the cumulative flow of
work?
Is the team likely to finish the
iteration on time?
Is the amount of work or
number of work items in the
iteration growing?
Does the team have too much
work in progress?
How is the team doing in
estimating work for the
iteration?
of Items
Work
# Hours
of Work
Status on All Iterations Report
•
•
•
•
Is steady progress being made across all iterations?
How many stories did the team complete for each iteration?
How many hours did the team work for each iteration?
For each iteration, how many bugs did the team find, resolve, or close?
Stories Overview Report (Agile)
•
•
•
•
How much work does each story require?
How much work has the team completed for each story?
Are the tests for each story passing?
How many active bugs does each story have?
Stories Progress Report (Agile)
•
•
•
How much progress has the team made toward completing the work for each story?
How much work must the team still perform to implement each user story?
How much work did the team perform in the last calendar period?
Requirements Progress Report (CMMI)
•
•
•
How much progress has the team made toward completing the work for each
requirement?
How much work must the team still perform to implement each requirement?
How much work did the team perform in the last calendar period?
Requirements Overview Report (CMMI)
•
•
•
•
How much work does each Requirement require?
How much work has the team completed for each Requirement?
Are the tests for each Requirement passing?
How many active bugs does each Requirement have?
Release Burndown (Scrum)
•
•
How much work remains in the release?
How quickly is your team working through the product backlog?
Sprint Burndown (Scrum)
•
•
•
•
How much work remains in the sprint?
Is your team on track to finish all work for the sprint?
When will your team finish all work for the sprint?
How much work for the sprint is in progress?
Unplanned Work Report
•
•
How much work was
added after the
iteration started?
Is too much work
being added during
the iteration?
Test Case Readiness Report
•
•
•
•
When will all the test cases be ready to run?
Will all the test cases be ready to run by the end of the iteration?
How many test cases must the team still write and review?
How many test cases are ready to be run?
Test Plan Progress Report
•
•
•
•
•
•
How much testing has the
team completed?
Is the team likely to finish
the testing on time?
How many tests are left to
be run?
How many tests are passing?
How many tests are failing?
How many tests are
blocked?
Streamline the Process
DASHBOARDS
Dashboards
• Quickly find important
information about team
projects
• Show project data, support
investigation, & help teams
perform common tasks more
quickly.
• Leverage SharePoint products
through Web Parts
– Excel Web Access
– Team Web Access
Dashboards
•
•
•
•
•
•
•
My Dashboard
Project Dashboard
Progress Dashboard
Quality Dashboard
Test Dashboard
Bugs Dashboard
Build Dashboard
My Dashboard
• What is the next set of Tasks, Bugs, or
Test Cases that I should act on?
• What is the status of the team's most
recent builds?
Project Dashboard
• Is the team likely to finish the iteration on time?
• Will the team complete the planned work
based on the current burn rate?
• What were the most recent check-ins?
Burn Rate
Work Item Breakdown
Burndown
Progress Dashboard
•
•
•
•
•
Is the team likely to finish the iteration on time?
Will the team complete the planned work based on
the current burndown?
How much progress has the team made on
implementing user stories in the past four weeks?
How quickly is the team identifying and closing
Issues?
What were the most recent check-ins?
Quality Dashboard
•
•
•
•
•
•
Is the test effort on track?
Is the team testing the appropriate functionality?
Are the team's bug fixes of high quality?
Are tests stale?
Does the team have sufficient tests?
Are any bottlenecks occurring?
Test Dashboard
•
•
•
•
•
•
Is the authoring of Test Cases on track?
Has the team defined Test Cases for all User Stories?
What are the proportions of Test Cases that are passing,
failing, and blocked?
Do test failure metrics indicate a problem that requires
further investigation?
What is the status of last night's build?
What are the most recent check-ins?
Bugs Dashboard
•
•
•
•
•
How quickly is the team resolving and closing bugs?
Is the team fixing bugs quickly enough to finish on time?
How many bugs is the team reporting, resolving, and
closing per day?
Is the team resolving priority 1 bugs before priority 2 and
3 bugs?
Does any team member have a backlog of priority 1 bugs
that warrant redistribution?
Build Dashboard
•
•
•
•
•
•
How volatile is the code base?
How much of the code is the team testing?
How high is the quality of the builds?
Is the quality increasing, decreasing, or staying constant?
Which builds succeeded?
Which builds have a significant number of changes to the code?
Streamline the Process
MICROSOFT TFS USAGE
Microsoft TFS Environment
Servicing organizations such as MSIT, DevDiv, Windows, SQL, AdCenter,
MSN/Windows Live, Bing Mobile, Windows Azure, MEDPG, and HED
Northern Ireland
Redmond
Scotland
Fargo
France
Hawaii
North Carolina
Visual Source Safe migration
Internal Usage
Instances
Team Project Collections
Team Projects
Active Unique Users
Work Items
Source Code Files
Shanghai
as of June 2012
52
313
10,101
42,687
15,502,244
191,608,280
Builds Per Month
3,023,416
Test Cases
3,023,416
Availability
99.83% uptime
6 proxy servers configured serving
a load of 100,000,000+ requests
per week.
700 GB SAN ea.
Hyderabad
Hardware-64-Bit Server 2008 R2
App Tier: 8-way, 2x HP ProLiant with
16GB of RAM running on 64-Bit
Windows Server 2008 R2
Data Tier-Single Instance: 24-way, 2x
HP with 128GB of RAM
Failover cluster configuration
400 dedicated spindles equaling 60 TB