This post originated from an RSS feed registered with Agile Buzz by Keith Ray. Original Post: Specification Documents as Tests Feed Title: MemoRanda Feed URL: http://homepage.mac.com/1/homepage404ErrorPage.html Feed Description: Keith Ray's notes to be remembered on agile software development, project management, oo programming, and other topics. Latest Agile Buzz Posts Latest Agile Buzz Posts by Keith Ray Latest Posts From MemoRanda

I was in a conversation with someone whose project is using Scrum. I was, if I remember correctly, trying to talk about the idea of how agile projects try to minimize the creation of artifacts not directly needed by the end-user or the developers.

She responded by talking about how essential the specification documents are for her team. I asked her "Who reads these documents?" and she said that the testers do. (NOTE: not primarily the programmers!) I then suggested to her that maybe in this agile development process, the testers should be writing these documents instead of reading them. And not writing them as static documents, but as executable tests in a form understandable by the Product Owner and programmers. Her face lit up with understanding.

I hope I helped. If she recognizes my attempt at recounting this conversion, I hope she will let me know if this helped her team in their adoption of agile practices.