Types of TFS work items: tasks or scripts, or use them?

Question

There are three types of work items in the default TFS setting: script, task, and error. This last one is quite simple, and the task is also: this is a specific job for a team member. But I think the script is a bit vague.

Usually I create a script for larger and more general units of work: for example, "Create functionality to add employee lines to the employer." Smaller, more specific work items will then be tasks, for example: "Create a part form", "Create a save method on the server", etc.

When I check for changes, I associate the change set with the AND script with a specific task. Is this a good habit? How do you solve tasks and scenarios? Any resources for best practices?

I also heard that the scripts are actually intended to be used, is that so?

Answer 1

Scripts can be any user story.

You only need to perform a task check. When tasks are created, they must first be bound to a script, and then assigned to developers.

Thus, the connection between the sessions and the script is automatic (and reporting).

No two way data processing

Answer 2

In the MSF Agile template, the scenarios can also be seen as " User History " - sort of like an easy flexible use case.

, , . , Qaru " " " ". MSF Agile (.. , ), , - .

, , . TFS 2010 , . (.. , , , ).

, , . , - .

, : http://www.woodwardweb.com/vsts/top_tfs_tip_3_r.html). , MSF Agile, , . , , , , - .

, .

Answer 3

" TFS " "MSF Agile Software Development", :

- , . persona , . ; . , .

, "/ " - .

Answer 4

You can think of scenarios as a representation of users, while tasks are the perspectives of developers. According to MSF Agile documentation, the scenario “represents one way of user interaction through a system under construction”, and the task “identifies” a specific work item for a team member to execute. ”

Tasks can be scripted. When you check, as a developer, you have solved the problem, not the script, so you need to associate a set of changes with this task.