Risk bears the potential that problems will occur, and risk is inherent in the development of any large software system. Some specific risks arise from the nature of the product being developed-for example, if the product is complex, or if testing is not feasible. Other risks flow from the development project itself-for example, if requirements change, or if cost or schedule constraints are imposed. A common approach to risk in software development is to ignore it, and hope that no serious problems occur; another is to respond to problems only if and when they occur. A more useful approach, however, and one with which some leading software development companies have been able to minimize and combat risks, is to use formal, quantitative risk-management techniques and processes. These techniques and processes are the subject of this book. Foreword by Tom DeMarco.