Risk identification is a systematic attempt to specify threats to the project plan (estimates, schedule, resource loading etc).
Methods used for Risk identification under Risk management One method for identifying risks is to create a risk item checklist. The checklist can be used for risk identification and focuses on some subset of known and predictable risks in the following generic categories:
Product Size – Risks associated with the overall size of the software to be built or modified.
Business Impact – Risks associated with constraints imposed by management or the marketplace.
Customer Characteristics – Risks associated with the sophistication of the customer and the developer’s ability to communicate with the customer in a timely manner.
Process Definition – Risks associated with the degree to which the software process has been defined and is followed by the development organization.
Development Environment - Risks associated with the availability and quality of the tools to be used to build the product.
Technology to be built - Risks associated with the complexity of the system to be built and the “newness” of the technology that is packaged by the system.
Staff size and Experience - Risks associated with the overall technical and project experiences of the software engineers who will do the work.
To Download: http://www.megaupload.com/?d=YPSOCIZY
To Download: http://www.megaupload.com/?d=YPSOCIZY
No comments:
Post a Comment