Comment Doesn't work for most internal software developmen (Score 1) 681
For a couple of reasons:
1) At the beginning of some new programming project desired by somebody on the business side, the programmer will frequently not have sufficient domain knowledge to assist in coming up with complete specifications. For example, I used to work for a company that maintained demographic and and circulation fullfillment databases for B2B pubs (everything from Information Week to Concrete Construction.) With the more complicated reports that business side people asked for, I couldn't foresee the ambiguities in the specifications until I began implementing them, since I had no particular prior experience in the domain. And the business side people didn't necessarily understand the notion of "precise specification."
2) Speed matters. Even a couple of weeks can make the difference between a rousing success and so-so release in some instances. This is certainly true in the trading industry, where I work now.
1) At the beginning of some new programming project desired by somebody on the business side, the programmer will frequently not have sufficient domain knowledge to assist in coming up with complete specifications. For example, I used to work for a company that maintained demographic and and circulation fullfillment databases for B2B pubs (everything from Information Week to Concrete Construction.) With the more complicated reports that business side people asked for, I couldn't foresee the ambiguities in the specifications until I began implementing them, since I had no particular prior experience in the domain. And the business side people didn't necessarily understand the notion of "precise specification."
2) Speed matters. Even a couple of weeks can make the difference between a rousing success and so-so release in some instances. This is certainly true in the trading industry, where I work now.
