> What changed at Pivotal labs? The bread and butter of Labs is teaching people pair programming and TDD. So I was taught those things, and I'm still learning.

> What changed at Pivotal labs? The bread and butter of Labs is teaching people pair programming and TDD. So I was taught those things, and I'm still learning. It takes a few passes through the whole cycle of story->feature test->integration test->unit test for things to begin to click, for that way of thinking to become habitual. It is uncomfortable and frustrating for some time, as Ian Sommerville found. In fact, because most code is not written test-first, it is difficult to test. So all that keeps you to TDD is habit and, to some degree, help from another engineer. > And what do you get with regards to specs? It seems to me the methodology fits how requirements are derived. The most popular story-writing style I have seen so far is the As A/I Want/So I; Given/When/Then. Usually some acceptance criteria are supplied. To varying degrees of fidelity that the feature tests will typically follow Given/When/Then. In our weekly Iteration Planning Meetings engineers are expected to pipe up if there are useful ways to decompose stories into smaller stories, which makes the overall situation more manageable.