Given a short (2-week) sprint, is it ever acceptable to forgo TDD to "get things done"?
- by Ben Aston
Given a short sprint, is it ever acceptable to forgo TDD to "get things done" within the sprint.
For example a given piece of work might need say 1/3 of the sprint to design the object model around an existing implementation. Under this scenario you might well end up with implemented code, say half way through the sprint, without any tests (implementing unit tests during this "design" stage would add significant effort and the tests would likely be thrown away a few times until the final "design" is settled upon).
You might then spend a day or two in the second week adding in unit / integration tests after the fact.
Is this acceptable?