John Galt 2007

The product manager asked me this question and it seems legitimate. I can understand the relationship between issues and tasks insofar as an issue can be translated into one or more tasks (and should be linked... is it )

However, isn't a bug a type of issue



Re: Team Foundation Server - Work Item Tracking What is the difference between issues and bugs?

Ninoslav Rasinec

Well, technically you are right - bug can be type of issue - it is all determined by the way how development process is organized in your team. Bug can also be translated into one or more tasks. As far as I can understand, task represents ※unit of work§ which must be done in order to solve all other work item types. For example, if you enter scenario or requirement or issue or bug in your TFS than it only represents your plan (your need) to do something; but 每 when members of your team actually must do some work, than you must assign them tasks 每 one or more for each of your scenarios, requirements, issues or bugs.

OK 每 that all sounds well in theory, but, on the other hand, I can tell you one thing for sure 每 there is a lot of teams that adopts development methodology to the practical aspects of their development process. And 每 if there is bug in the application, why can*t I assign bug to one of my developers instead of creating new task and linking them together, right Yes 每 right, but situation is more complicated than that; you are misusing process template and methodology which is there to help you organize your team, or your team is well organized but you feel that you do not need more ※paper work§ in order to get thing done and so on#

Please take a look at Team Development with Visual Studio Team Foundation Server guide (http://www.codeplex.com/TFSGuide) in which you can find this descriptions for work items:

MSF for Agile Software Development Process Template

The work item types provided by this process template include:

Scenario 每 Used to represent a user interaction with the application system. It records the specific steps necessary to reach a goal. When writing scenarios, be sure to be specific as there may be many possible paths.

Task 每 Used to represent a unit of work that needs to be performed. Each role has its own requirements for a task. For example, a developer uses development tasks to assign work.

Quality of Service Requirement 每 Used to document the system characteristics such as performance, load, availability, stress, accessibility, and serviceability

Bug 每 Used to communicate a potential problem in the system.

Risk 每 Used to identify and manage the inherent risks of a project.

MSF for CMMIR Process Improvement Process Template

The work item types provided by this process template include:

Requirement 每 Used to capture the requirements defined during the requirements gathering phase.

Change Request 每 Used to capture any change requests subsequent to the gathering of requirements.

Issue 每 Used to capture issues to be tracked in the projects.

Task 每 Used to represent a unit of work that needs to be performed. Each role has its own requirements for a task. For example, a developer uses development tasks to assign work.

Review 每 Used to represent the review work units with in the projects, like code review, design review etc.

Bug 每 Used to communicate a potential problem in the system.

Risk 每 Used to identify and manage the inherent risks of a project.

Ninoslav Rasinec
ApplicationAspect.com