Identifying risks associated with software development is vital for project success. In most cases, developers are aware of risks throughout development but potential problems are not communicated in a way that reflects uncertainty in project health.
Taxonomy-based risk identification is a loosely structured method for quantifying risks during the planning phase(s) of software development.
Process
A project manager interviews developers using a questionnaire to identify risks in different project areas. These areas are referred to as “classes”.
Advantages for Adopting this Method
- Risks are identified earlier in the project
- Formal procedures exist for risk identification which helps reduce the ad-hoc nature of typical risk identification in software projects
Dangers of Adopting this Method
- Inexperienced or untrained developers will not be able to identify risks properly
- Uptraining may take time away from critical project activities
- Inexperienced teams usually lack defined risk management procedures
References
http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr06.93.pdf
This PDF contains the TBRI abstract and the following topics:
- Background and motivation for introducing a taxonomy-based approach
- Results of studies which were used to refine TBRI
- Sample approaches for introducing TBRI into your company and project routines
- Sample interview questionnaires