After reading the first couple chapters (from the website), I realize that you are arguing for all the things that I have been advocating at my current position. We are making a move here at my company to become better at the requirements portion of change requests by implementing FitNesse as part of our development practices and trying to get the QA staff and other stakeholders (project managers, clients) involved early in the process.
That being said, would you say that the groups who would benefit the most from your book be the developers, or those folks who normally shy away from the software development until later in the traditional cycles?
posted 4 years ago
I've tried very hard to make the book readable and understandable to developers, testers, analysts and business people alike. there is one chapter on automation that might be a bit too much for non technical people, but that is clearly marked as such and I advise non techies to skip over it as they won't be interested in automation that much. the rest of the book seems to be well received by many different roles.