Scrum for Team System Guidance / Version 3 / Bug
Work Item: Bug
Description:
In the version 3 template bugs have a new home. In previous scrum templates, the bug work item has lived in the sprint backlog and even the product backlog. Neither of these homes felt completely comfortable as the bug work item became either just a task or backlog item with additional meta data.
Now the bug work item is an entity in it's own right. It has a single concern and deals with the one thing it should, the description of the error condition. No actual work is tracked against the bug work item itself, instead backlog items or tasks should be created to handle the work that needs to completed (because that's their job).
Modeling Bugs In SfTS v3:
Bugs also have a special relationship with Acceptance Tests. When bugs are linked to ATs using the Fails linkage, the bug work item status directly affects the status of the test. A test cannot be Passed if it has active bugs.
Bugs are also a component of the Microsoft Test Manager interaction, along with Acceptance Tests.
Screen Shot:
Fields:
| Field Name | Description | Data Type |
|---|---|---|
| Title | A short description of the error condition. | Text |
| Description | The detailed description of the bug. | Text |
| Testing Impact |
The perceived severity of the bug. Possible values are:
|
Drop down list |
| State | This is the status of the Acceptance Test Item as selected by the Product Owner or QA | Drop Down List |
| Area | The Area Path can be used to categorise the bug | Project Path |
| Iteration | The iteration Path of the bug. | Project Path |
| Date Found | The date when the bug was found. This field is populated automatically. | Date Time |
| Activated By | The work item creator. This field is populated automatically. | Project User |
| Date Closed | The date the bug was set to closed. This field is populated automatically. | Date Time |
| Closed By | The user that set the bug to closed. This field is populated automatically. | Project User |
| Found | The build that the bug was found in. | Drop Down List |
| Fixed | The build that the bug was fixed in. | Drop Down List |
| System Info | A description of the system condition that the bug was found in. This could detail operating system, other installed software or any other external system that could affect the error behavior. | Text |
| Steps to Reproduce | A detailed list of the steps needed to reproduce the error condition. | Text |
Work flow:
