Beruflich Dokumente
Kultur Dokumente
Paula Duchnowski CQA, CSTE paula.duchnowski@generalcasualty.com General Casualty Insurance May 9, 2002
What is Risk?
A potential problem waiting to happen May adversely impact schedule, cost, objectives Will vary in probability, impact and timeframe
Project Objectives: Increase consistency among all software development projects Utilize processes that will increase the probability of project success
Identifying Risks
Various publications Consider three and organizations perspectives: have developed Project Management and staffing generic risk categories and generic checklists. Technical Checklists help assure Quality of Product arent overlooking something
Tactical Considerations
Budget Schedule & Resource availability Estimating risks and expertise Vendor Management Adequacy of Methodology / Project process Communication Project Size & Sponsorship and Complexity high-level support
Technical Perspective
Data Conversion: (GIGO) System Interfaces Operations / Postimplementation Support New or unproven Technology Implementation & rollout Infrastructure support Adequacy of Infrastructure Legacy Impacts / Support
Quality Risks
How well will product meet expectations?
Ease of Use Data Integrity Understand impact to users
Defects in production
Statement of Risk
May need to Drill Down to determine the real risk to the project:
Asking Why? Why is this situation a risk to the project? What is the worst case scenario if the risk is realized? Some less than ideal circumstances may not be true risks
Discussion
Case Study: Enhancing and enforcing the Software Development Life Cycle What are some of the risks? (be creative- pretend you know this company)
Quantifying Risk
Early in Project
More difficult to be precise Establish risk order of magnitude Continue to revisit as part of risk management process
Simulation:
Prototype what if scenarios
Quantifying Risk
Define scale you will be using for Probability and Impact Try to define scale to correspond to key objectives and constraints Look at example Checklist
Discussion
Discuss possible mitigation strategies for case study risks
Periodic meetings / updates regarding risk status Periodic re-assessment of risk exposure Update Risk data and project plan
Summary
Why Risk Management is Important Steps of a Risk Management Process
Identify Project Goals & Objectives Identify Risk Analyze Risk Plan for Risk Control Risk
Thank you
Bibliography
Project Management Institute: Project Management Body of Knowledge Keil, Mark; Cule, Paul; Lytinen, Kalle; Schmidt, Roy: A Framework for identifying software project risks: Communications of the ACM, November 1998 Hall, Elaine. Managing Risk. Methods for software systems development. Reading, MA: Addison-Wesley Publishing, 1998. Jones, Capers. Assessment and Control of Software Risks, 1994. Mulcahy, Rita, Managing and Estimating Project Risks, September, 1999.