Take the 2-minute tour ×  My team at work is moving to Scrum and
other teams are starting to do test-driven development using
unit tests and user acceptance tests. I like the UATs, but I'm
not sold on unit testing for test-driven development or test-
driven development in general.  It seems like writing tests is
extra work, gives people a crutch when they write the real code,
and might not be effective very often.  I understand how unit
tests work and how to write them, but can anyone make the case
that it's really a good idea and worth the effort and time?
Also, is there anything that makes TDD especially good for
Scrum?  share|improve this question If you would like to make
sure that your software breaks down frequently, is more-or-less
completely unmaintainable, and is due for replacement before
it's actually ready for production; then I would suggest you
dispense with unit testing entirely, and never take the time to
learn TDD. –  David Wallace Mar 17 '12 at 8:17 Think about the
wish/need for a refactor.