This document introduces Scrum and Visual Studio Team Foundation Server (TFS) Scrum 2.0. It describes the different work item types, queries, and reports available in TFS Scrum 2.0 and how they map to Scrum concepts like product backlog, sprint backlog, tasks, and burndowns. It also provides tips on using tasks, bugs, and the sprint burndown chart in TFS. Finally, it briefly describes the backlog page and components of the TFS web access interface.

1. Agile Series by Nishanth
introducing
Scrum and TFS

2. What’s there in Visual Studio Scrum 2.0?
Work Item Types Queries Reports
Product Backlog Item Product Backlog Backlog Overview
Task Feedback Requests Release Burndown
Code Review Request Current Sprint Sprint Burndown
Code Review Response Blocked Tasks Velocity
Feedback Request Open Impediments Build Success Over Time
Feedback Response Sprint Backlog Build Summary
Impediment Test Cases Test Case Readiness
Test Case Unfinished Work Test Plan Progress
Shared Steps Work in Progress

3. Scrum and VS Scrum 2.0 Template – What’s what
Scrum Concept Visual Studio Scrum 2.0
Team Security groups created in TFS
Definition of Done Either a Wiki entry or a document stored in SharePoint/repository
Product Team Project
Product Backlog Product Backlog shared query or Backlog page on TWA
Product Backlog Item PBI or Bug work item types
Acceptance Criteria Acceptance Criteria field inside PBI/Bug WI types
Release Iteration Path (high level)
Release Plan Backlog page on Team Web Access (w/ Forecast tool)
Sprint Iteration Path (low level)
Sprint Goal Either a Wiki entry or a document stored in SharePoint/repository
Sprint Backlog Sprint Backlog shared query or Backlog & Board pages on TWA
Task Task work item type
Burndown and Velocity Release Burndown, Sprint Burndown, and Velocity reports and charts on TWA
Impediment Impediment work item
Retrospective Either a Wiki entry or a document stored in SharePoint/repository

4. Components of TFS Web Access

5. The Backlog Page
• Shows Product and Sprint Backlogs
• Easy to Add
• Drag and drop
• Highly Customizable
• Priority field to persist the order

6. The (Sprint) Backlog Page
• Shows forecasted PBIs & Bugs and linked tasks
• What’s not important: Capacity, work by
Activity & Assigned To

7. The PBI Work Item Type

8. The Task Work Item Type
• Small enough to be completed in one day
• Estimated in hours
• Update only remaining hours
• Avoid using the Activity field
– All activities are “development”

9. The Bug Work Item Type
• A bug work item is the report of a bug in the product
• Similar to a PBI
Tip: Prefix the bug with “Bug:” So they are identifiable in the Product Backlog

10. Sprint Burndown
• Shows everyday progress in a chart format

11. Thanks!
Exciting new transitions