Awesome- thanks for the info. I tried out specflow writing a few scenarios for a feature that I worked on recently- I'm already a huge fan. And darn it if I didn't find a small defect (one of those- "It won't happen in production, but conceptually it's not quite right" kinds of things).

One problem that we've been having is that the PM's great value to this project is she has more business knowledge of what we are building than anyone else. This has led to a great strain on her time as she tries to make sure she verifies absolutely everything we do and that there are no gaps in dev/QA's understanding of business logic. Executable specs would be an enormous benefit to her (at least I think so) because it would be easy to review QA's understanding of the problem we are trying to solve- and do it without requiring a demo or calling a meeting.

I'll admit that I am slightly proud that our app is organized well enough to really take advantage of this- that is that our business logic all exists server side so it can be verified without requiring the client. Individual modules of our code base may be difficult to work with, but the overall structure is very well done (imo). I'm also thinking about how we can use this client side as well- we have absolutely no automated regression testing because we burned about a month and a half trying to get Telerik's Silverlight automated testing tools working with very little success. This would let us test from the viewmodel down- I'm not sure if we could actually hook into the actual views or not. Either way- there's definitely a lot of potential here, and I'm glad this came up. I don't know if it will get us to two teams (it may- this might allow us to have a bank end/front end separation), but if not there's potential to alleviate a lot of other strain on the project.