title: TFS work item types: tasks vs. scenarios, or use both?
body: <p>In the default TFS setup there are three work item types: scenario, task and bug. That last one is quite straightforward, and task also: it's a specific job for a team member to complete. But I think scenario is a bit vague.</p>
  
  <p>I usually create a scenario for larger and more general units of work: for example "Create functionality to add employee lines to an employer." Smaller, more specific work items would then be tasks, for example: "Create detail form.", "Create save method on server.", etc</p>
  
  <p>When I check in changes I link the changeset to the scenario AND to the specific task. Is this a good habit? How do you deal with tasks and scenarios? Any resources to best practices?</p>
  
  <p>I've also heard scenarios are actually meant for use cases, is this so?</p>