Visual Studio Scrum 1.0
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:
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 Explorer or on the team project portal.
Monitoring and Reporting Team Progress
You can use the reports in the following table to track team progress and velocity.
Note
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 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.
Track team burndown for backlog items and tasks
Track team velocity
Track build activity, success, and trends
Track testing activity
Additional Resources
Planning and Tracking Projects
MSF for Agile Software Development v5.0
Agile Principles and Values, by Jeff Sutherland
Tracking Bugs, Tasks, and Other Work Items
Adding and Modifying Bugs, Tasks, and Other Work Items
Choosing Link Types to Effectively Track Your Project
Creating Relationships Between Work Items and Other Resources
Customizing Team Projects and Processes
Customizable Process Guidance – Visual Studio Scrum 1.0 on the Microsoft website
Microsoft How-To: Scrum for Everyone on the Visual Studio Magazine website