Before All Else Fails
In the software development world, conventional wisdom holds that when something new is not working as expected, the trouble can usually be traced to inadequate requirements gathering, faulty design or user error. In the infamous “some assembly required” scenario, the customer actually gets involved in final “construction” and user acceptance testing. While this approach may have some advantages, overeagerness to begin using the product at once may lead to rushing and avoidable mistakes. Such mistakes are compounded when in a quest to…