Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 1
    So basically what you're saying is that TDD improves the development effort by encouraging stakeholders to do those things that they should be doing anyway, like providing clear, actionable requirements and acceptance criteria. Commented Sep 7, 2013 at 0:36
  • 1
    Well, not just that. As the project progresses the increased participation allows for a better conversation between dev and stakeholders. It allows for things like dev offering less costly alternates as their understanding of what the stakeholder wants get refined further. It allows stakeholders to change requirements earlier as they realize things are missing, or won't work without such an antagonistic response from dev; and without many of the unreasonable expectations that usually come from stakeholders. Commented Sep 8, 2013 at 7:00