RiskList.docVIP

dbViZ Risk List Version 1.2 Revision History Date Version Description Author 10/28/2002 1.0 Initial draft for feedback Ross Paul 11/13/20002 1.1 Addition to the more identified Risk Elements Sonia Kaura 12/09/2002 1.2 Addition of the elements after the review Sonia Kaura Table of Contents 1. Introduction 4 1.1 Purpose 4 1.2 Scope 4 1.3 Definitions, Acronyms, and Abbreviations 4 1.4 References 4 1.5 Overview 4 2. Risks 4 2.1 Project Risk: Hard Deadline 4 2.1.1 Risk Magnitude 4 2.1.2 Description 4 2.1.3 Impacts 4 2.1.4 Indicators 4 2.1.5 Mitigation Strategy 4 2.1.6 Contingency Plan 4 2.2 Technical Risk: Staff Inexperience 4 2.2.1 Risk Magnitude 4 2.2.2 Description 4 2.2.3 Impacts 5 2.2.4 Indicators 5 2.2.5 Mitigation Strategy 5 2.2.6 Contingency Plan 5 Risk List Introduction Purpose The purpose of the Risk List is to support the development of the Database Visualizer, henceforth “dbViZ” System by documenting potential risks, their magnitudes, and mitigation strategies. Scope This risk lists addresses the entire dbViZ project. Definitions, Acronyms, and Abbreviations See glossary References None Overview The risks known at the publication date of this document are listed below, along with mitigation strategies for each risk. Risks Project Risk: Hard Deadline Risk Magnitude Severe Description Two hard deadlines are built into this project by its scholastic nature. Given these deadlines functional requirements may not be met. Impacts An incomplete product, a bad grade, end of project in December. Indicators Falling behind in the Software Development Plan. Mitigation Strategy Hard and fast milestones are being established so we can complete the breadth and the depth needed to fulfill the requirements. Contingency Plan If project falls too far behind, the developers will begin to spend more time developing dbViZ, sacrificing some documentation. If this does not remedy the situation, the Architect will quit his day job in order to devote even more t