Sprints with Scrum for Team System
Each Sprint in Scrum for Team System is represented by a matching combination of a node in the
Iteration Path hierarchy and a Sprint Work Item. The Iteration Path allocates sets of Sprints
into a given Release, while the work item provides configuration for the Sprint attributes,
including the Sprint start and end dates. When first setup, a Scrum for Team System project will
create a set of template Releases and Sprints which can easily be customised to fit your specific project.
For information on customising the default Release and Sprint hierarchy, please see the
Configuring Releases in Scrum for Team System section.
Sprint work items can be created and modified using the Team Explorer interface running in Visual Studio or alternatively
by using the Team System plug-in for Microsoft Excel. The second method is ideal for working with a number of Sprints
in one operation, like for example, setting the start and end dates for ten Sprints in one go. Excel is also a more natural
interface for those team members who are not regular users of Visual Studio.
Modifying Existing Sprint Work Items with Team Explorer
Within Team Explorer, use the All Sprints query to list all the existing Sprints and select the one you want to update.
Change the desired fields and then hit the save icon.
An example of a Sprint Item being modified is shown below:
Creating New Sprint Work Items with Team Explorer
To create a new Sprint work item using the Team Explorer interface in Visual Studio,
right click on the Work Items folder of your Scrum project in the Team Explorer
window. A window will appear that may offer the option to "Add Sprint" in which
case select this option. Alternatively if this option is not available you will
find it in a further window by selecting "Add Work Item". See the screenshot below:
It is also possible to create a new Sprint through the "Team" drop-down menu.
Sprint Work Item Fields
The minimum fields required for Scrum for Team System to successfully drive its reports are the Sprint Name,
Sprint Start Date and Sprint End Date. Creating multiple Sprint work items with the same Sprint Name or
overlapping date ranges will cause unpredictable output within the reports.
All the fields of a Sprint work item are shown in the table below:
| Field Name |
Type |
Required |
Description |
| Sprint Name |
Iteration Path |
 |
This field must point at the matching Sprint configured under the correct Release within the Iteration Path hierarchy |
| Capacity |
Number |
|
Team work capacity for the Sprint in hours |
| Sprint Start Date |
Date/time |
|
First working day of the Sprint |
| Sprint End Date |
Date/time |
|
Last working day of the Sprint |
| Current Status |
Workflow |
|
Not Done - In Progress - Done - Cancelled - Deleted |
| Sprint Goal |
Tab/Text |
|
Describes the Sprint Goal |
| History |
Tab/Text |
|
Shows the change history of the Sprint work item, generated by Team System. Can be augmented with manually added text |