Risk Item Checklist

To identifying risks is to create a risk item checklist. Checklist can be used for risk focuses and identification on some subset of predictable and known risks in the following generic subcategories.

Product size - the risk will be associated with the overall size of the software to be built or modified

Business impact - the risk will be associated with constraints imposed through management or the marketplace

Customer  characteristics  -  the risk will be associated  with  the  sophistication  of  the  customer  and  the developer's capability to communicate with the customer in a timely manner.

Process definition- the risk will be related with the degree to that the software process has been defined and is followed by the development organization.

Development environment - the risk will be related with the quality and availability of the tools to be used to build the product.

Technology to be built - the risk will be associated with the complexity of the system to be established and the newness of the technology that is packaged by the system.

Staff size and experience - the risk will be associated with the overall project  and technical experience of the software engineers who will do the work.

The risk item checklist can be organized in various types. Questions relevant to each of the topics noted above can be answered for each software project. A different risk item checklist format simply lists characteristics that are relevant to each generic subcategory.  Answers to these questions allow the planner to estimate the impact of risk. At the final stage asset of risk parts and drivers are listed along with their probability of occurrence.