ABSTRACT
In-house development has a mixed reputation. In some companies, it is the only option considered. Elsewhere there are horror stories about years lost due to poor quality systems developed by unqualified in-house staff. Earlier in the book several drivers were identified behind why in-house can be the right option in some circumstances. But the general IT industry sentiment in 2013 is that when all else is held equal, buying is better than building. For those who have strategic reasons to build their own software, this chapter reviews best practices on several key topics. It does not address all details, and especially leaves out general IT development considerations which affect any in-house development. If that level of background is needed, it is likely a warning sign that in-house development staff are not ready to do this kind of software anyway.
