title: Breaking down tasks of user stories between developer and QA
body: <p>My team have recently gone to sprints and we are going through breaking down our user stories into tasks.  What is the best practice in breaking down the user stories?  </p>
  
  <p>Should each task include developing, design, testing, and so forth?  Or can the tasks be individually broken out?  If so, should the tasks that aren't testing related just go straight to done and skip "Verify" or "To Test" column in the workflow?</p>
  
  <p>From what I've read online it seems there is no 'set' way and people do it differently.  I'm curious if people have had problems with their way of doing it.</p>
  
  <p>Any help would be useful!</p>