[crdoconnor]

>The burden of proof usually lies on the person suggesting a change to an existing process. What arguments would you give to try to convince someone to do TDD?

Arguments don't work. You need to build the tools that let your developers actually write sensible tests (i.e. tests which mimic user stories).

Once the tools are there the process becomes fairly natural and the upsides become obvious.

Some people call this BDD. It doesn't really matter what it's called, but it's generally a faster and less risky approach to programming.