This template lists potential risks that are common with software that automates the installation of software applications. 

Software testing and quality are vitally important topics--but they are also deadly dull, real yawners the way most people talk about them. In this column, the author explains why that is so, and offers some suggestions on how to overcome the problem. Basically, he says, people are trying to make a managerial sow's ear out of a technical silk purse.

Testing is often seen as an effort to determine the quality of the product at the end of a project, so it needs to be executed when development has finished instead of being a means to deal with risks at the earliest stage possible. Therefore, project budget, is in most cases spent on the processes that actually produce tangible products, at the expense of the testing budget. Whatever budget is left for testing will be spent on people rather than on test tools, especially since most of the mainstream tools are often perceived to be too expensive. A solution to this may be found in the use of open source test tools. With no license fees, the use of open source tools can provide a customer some of the benefits of test automation, without the costs.

This Software Inspection Master Plan template is a revised version from the original in Gilb & Graham's book, Software Inspection. This template is partially filled out to give you an exmple of how to use it.