Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 3
    The best spec in the world is completely useless if the implementation does not reflect it. This is what happens when design specifications are done by people who are not involved in implementation. Commented Dec 7, 2011 at 20:18
  • 1
    This is very true. The trick, however is finding the right balance. Commented Dec 8, 2011 at 13:58
  • Your statement is true in some worlds. In many other worlds, the biggest cost of software projects is the business opportunity cost of every day that the product is not shipped. Delaying the launch of a company, for example, can kill the window of opportunity it is trying to exploit. Of course, shipping a piece of crap can be just as fatal. But front-loading the work into spec design is really heading down a slope to late, buggy projects that nobody likes, including the developers. Commented Feb 2, 2012 at 16:53