title: Is Scrum possible without test driven development?
body: <p>I have now witnessed two companies move to agile development with Scrum.  </p>
  
  <p>In both cases the standard of coding was good enough when each part of the application was only being worked on by one or two developers with the developers spending a reasonable amount of time working on one part of the application before moving to the next task. The defect rates were also reasonable.</p>
  
  <p>However with Scrum the developers are expected:</p>
  
  <ul>
  <li>to all be able to work on all the bits of the application.</li>
  <li>to only work on one area of the application for a few days at most before moving to the next area</li>
  <li>to mostly work on code they did not write</li>
  </ul>
  
  <p>Code qualities became an issue in both of the Scrum projects.</p>
  
  <p>So is there a way to do Scrum that does not lead to these problems, without first getting all the developers to do test driven development?</p>
  
  <p>Have you seen Scrum work well on a large project without test driven development?  (If so how?)</p>