Visual Studio Scrum 1.0

Makale
07/22/2011

You can develop complex products by using the Scrum framework, which is based on agile principles and values. For more information, see Scrum and Agile Principles and Values, by Jeff Sutherland.

Your team can practice Scrum more easily by using the artifacts in Microsoft Visual Studio Scrum 1.0. Each artifact serves a specific function and provides opportunities to refine your processes over time. These artifacts include work items, reports, and team queries, and your team can use them to track information, analyze progress, and make decisions.

You can download Visual Studio Scrum 1.0 from the following page on the Microsoft website: Microsoft Visual Studio Scrum 1.0. For more information about how to install this template, see the following blog entry on the Microsoft website: Microsoft Visual Studio Scrum 1.0.

In this topic

Defining and Tracking Work Items
Monitoring and Reporting Team Progress

Defining and Tracking Work Items

You can use work items to track, monitor, and report the development progress of a product and its features. A work item is a database record that you create in Visual Studio Team Foundation Server to record the definition, assignment, priority, and state of work. The process template for Visual Studio Scrum 1.0 defines the following types of work items:

Product backlog item
Bug
Task
Sprint
Impediment
Test case
Shared step

You can specify and update information for each work item on the form for that item. You can access artifacts either from the team project node in Team Exploreror on the team project portal.

Tasks	Related content
Track product requirements. Your team defines and updates product backlog items to capture the requirements of your product and track their progress.	Product Backlog Item (Scrum)
Open and track bugs. Your team defines and updates bug work items to track defects in the product. When you define a bug work item, you must report the defect accurately and precisely enough that other members of the team can understand the full impact of the problem.	Bug (Scrum)
Track and estimate tasks. Your team defines and updates tasks to track the level of effort that is required to implement a product backlog item. Tasks should represent a small unit of work. You can redefine larger tasks as smaller subtasks.	Task (Scrum)
Track sprints. Your team defines sprint work items to capture the goal or goals, the start and end dates, and the retrospective results for each sprint in your project.	Sprint (Scrum)
Define and manage impediments. Your team can create impediment work items to define known or potential problems and risks to your project.	Impediment (Scrum)
Test the application. Your team can define test case work items to specify tests that will support testing of product backlog items. You can define manual or automated test cases. Manual test cases specify a sequence of action and validation steps to run, and automated test cases reference an automation file.	Test Case (Scrum)
Define shared steps. Your team can define shared steps to more easily specify and maintain manual test cases. When you define shared steps, you specify a sequence of action and validation steps to run as part of a test case. Many tests require that you perform the same sequence of steps for multiple test cases. By creating shared steps, you can define a sequence of steps one time and insert it into many test cases.	Shared Steps (Scrum)
Find and list work items. You can manage your workload more easily by using built-in queries to find the product backlog items, tasks, impediments, and other work items for which you want to take action.	Team Queries (Scrum)

Monitoring and Reporting Team Progress

You can use the reports in the following table to track team progress and velocity.

Not

These reports require that the team project collection that contains your team project was provisioned with SQL Server Reporting Services. These reports are not available if Report Reports does not appear when you open Team Explorer and expand your team project node. Also, to view these reports, you must be assigned or belong to a group that has been assigned the Browser or Team Foundation Content Manager role in Reporting Services. For more information, see Add Users to Team Projects or Managing Permissions.

Tasks	Related content
Track team burndown for backlog items and tasks. You can track how quickly your team has completed work and how much work remains in a product backlog or in a sprint backlog by reviewing a release burndown report or a sprint burndown report.	Release Burndown (Scrum) Sprint Burndown (Scrum)
Track team velocity. You can track how much effort your team has completed for each sprint by reviewing its velocity report. You can also predict how much backlog effort your team can exert in future sprints if your team composition and sprint duration stay constant.	Velocity (Scrum)
Track build activity, success, and trends. You can track the quality and success of your team’s builds over time by reviewing build reports.	Build Success Over Time Report Build Summary Report
Track testing activity. You can track the team’s progress toward developing test cases, and you can determine how well the team covers its user stories if you review test reports.	Test Case Readiness Report Test Plan Progress Report