While your question is about "doing TDD properly", do you mind if I suggest another approach? Consider embracing a Risk Driven Development[0] philosophy. This

While your question is about "doing TDD properly", do you mind if I suggest another approach? Consider embracing a Risk Driven Development[0] philosophy. This is where the highest risk to a project's success is addressed first, then the next highest, and so on, which drives risk to 0 and success to 1. This begs the question, "what is typically the highest risk to a project's success?" This is always defining the (stakeholder) problem to solve. IOW, what would be the result if everyone involved had perfect knowledge of what needs to be done? From there, identification of what needs to be done next (risks/tasks/work/etc.) will flow. Note that risks include non-technical concerns. Many times these are some of the biggest risks. HTH 0 - https://www.methodsandtools.com/archive/agilesoftwarearchitecture.php https://www.methodsandtools.com/archive/agilesoftwarearchite...