(Due Disclosure: Ex ThoughtWorker) Pat is certainly very sharp and thinks deeply about issues. So are many other ThoughtWorkers, he is not alone. But otoh, T

(Due Disclosure: Ex ThoughtWorker) Pat is certainly very sharp and thinks deeply about issues. So are many other ThoughtWorkers, he is not alone. But otoh, TW also has a minority of dogmatic agile/TDD etc people for whom such practices are close to religion and any other approach is blasphemy. It seems you might have run across some of them. The best way for a client to use ThoughtWorks is to get their team to work on a chunk of software, keep them from switching taleted developers out for more junior folks, and add a couple of client devs to that team for a few months at a time. This ensures high quality and osmosis of practices without the kind of high pressure conversion tactics you seem to have experienced. ThoughtWorks is a great company and has many talented and thoughtful devs, but if you are paying them you have to pay attention to how they work and not let a few bad apples run amok and destroy your team morale. Just my 2 cents.