Timeline for Are there any best practices regarding the handover from architecture to development?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 2, 2012 at 16:53 | comment | added | Bill Gribble | 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. | |
| Dec 8, 2011 at 13:58 | comment | added | Michael | This is very true. The trick, however is finding the right balance. | |
| Dec 7, 2011 at 20:18 | comment | added | maple_shaft♦ | 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. | |
| Dec 7, 2011 at 18:34 | history | answered | Jere | CC BY-SA 3.0 |