SlideShare une entreprise Scribd logo
1  sur  23
Télécharger pour lire hors ligne
Risk analysis
   Risks are potential problem/uncertainty that might
    affect the successful completion of a software project.
   Risk analysis and management are intended to help a
    software team understand and manage uncertainty
    during the development process.
   The work product is called a Risk Mitigation,
    Monitoring, and Management Plan (RMMM).
 Two risk Strategies :
1. Reactive strategy
  Software team does nothing till the risk becomes
  real.
2. Proactive strategy
  Risk management begins long before technical
  work starts.
  Risks are identified and prioritized by importance.
  Then team builds a plan to avoid risks if they can
  or minimize their probability of occurrence or
  establish plan if risks become real.
 Categories of risks
1.         Project risks
  ◦ Threatens the project plan.
  ◦ If project risk becomes real, it is likely project
     schedule will slip and the costs will increase
  ◦ Identifies problems related to budgetary,
     schedule , personnel and resource

2.             Technical risk
  o     Threatens the quality of the software to be
        produced.
    o   Identifies problems related to design,
        implementation, maintenance etc
3.Business risk
•  Threatens the viability of the software to be built.
• Eg of business risk

4. Building an excellent product that no one wants.

5. Building a product that no longer fits into the
   overall business strategy.
6. Building a product that the sales force do not how
   to sell.
7. Change of management

8. Losing budgetary
  Steps for risk analysis
2. Risk Identification
• Lists the risks associated with a specific project.
• Use a risk item checklist to identify risks

   Risk item check list – A set of questions relevant to each risk.
A project manager attains a feeling of staffing risk by answering
the following set questions---
8. Are enough people available ?
9. Are the best people available ?
10.Will the project team members be working full time / part time
   on the project ?
11.Have the staff members received necessary training?
No. of negative responses to the questions ∝ degree to which the
   project is at a staffing risk
2. Risk projection
•  Also called risk estimation.
• Rates each risk in 2 ways :

4. Find the probability of occurrence of each risk.

5. Find the impact of the problems associated with each risk.

Steps 1 : Prepare a risk table.
a) Lists all risks identified in the first column.
b) Category of the risk is identified in the second column.
                 PS – project size risk.
                 TE – Technical risk.
                 BU – Business risk.
c) Probability of occurrence is entered in the third column.
   Individual team members are polled for their estimates in a
   round robin fashion until a single consensus is obtained.
d) Impact of each risk on the 4 risk components is assessed .
4 risk components are
1. Performance
If the risk becomes real will the requirements be met and will
the product be fit for its intended use?
2. Cost
If the risk becomes real will the project budget be maintained?
3. Support
If the risk becomes real will the resultant software be easy to
correct , adapt and enhance?
4. Schedule
Will the project schedule be maintained and the product will be
delivered on time if the risk becomes real?

The impact of each risk on the 4 components can be
categorized as
              1- Catastrophic
              2- Critical
              3- Marginal
              4- Negligible
The values are averaged to determine an overall impact value.
Table prior to sorting
•   Next the table is sorted by high probability
    and high impact.
•   Project manager defines a cut off line
    implying only risks above the line will be
    managed.
•   The column labeled RMMM contains a pointer
    into a Risk Mitigation Monitoring and
    Management Plan(A collection of risk
    information sheets developed for all risks
    that lie above the cutoff line)
Steps 2 : Assessing the risk impact .
a) Estimate the cost of each risk in the table.
• How to estimate the cost of each risk ?
Eg :
   Assume that the software team defines a project risk in the following
   manner:
  Risk identification. Only 70 percent of the software components
  scheduled for reuse will, in fact, be integrated into the application.
  The remaining functionality will have to be custom developed.
  Risk probability. 80% (likely).
  Risk impact. 60 reusable software components were planned. If
  only 70 percent can be used, 18 components would have to be
  developed from scratch (in addition to other custom software that
  has been scheduled for development). Since the average component
  is 100 LOC and local data indicate that the software engineering
  cost for each LOC is $14.00, the overall cost (impact) to develop the
  components would be 18 x 100 x 14 = $25,200.
b) Calculate the risk exposure foe each risk in the
  table ----
Risk exposure. RE = Prob. Of occurrence x cost of risk
                     =0.80 x 25,200 ~ $20,200.
c) Calculate the total exposure for all risks(above the
  cutoff line)

The total risk exposure provides a means for
adjusting the final cost estimates for a project.
If RE is greater than 50 % of the project cost ,
  the
viability of the project must be evaluated
3. Risk Refinement
•   During early stages of project planning, a risk may be stated
    quite generally.
•   As time passes and more is learned about the project and the
    risk, it may be possible to refine the risk.
•   One way to do this is to represent the risk in condition-
    transition-consequence (CTC)
•   Given that <condition> then there is concern that (possibly)
    <consequence>.
•   Using the CTC format for the reuse risk ----
•   Given that all reusable software components must conform to
    specific design standards and that some do not conform,
    then there is concern that (possibly) only 70 % of the planned
    reusable modules may actually be integrated into the as-built
    system, resulting in the need to custom engineer the
    remaining 30 % of components.
•   This general condition can be refined in the following
    manner:
    Sub condition 1
    Certain reusable components were developed by a third party with no
     knowledge of internal design standards.
    Sub condition 2
    Certain reusable components have been implemented in a language
    that is not supported on the target environment.
4. Risk Mitigation Monitoring and Management
All the risk analysis activities presented so far have single goal
i.e to assist the project team in developing a strategy to deal
with risk.
An effective strategy is--
6.   Risk Mitigation (avoidance)
For example,
Assume Risk -High staff turnover is noted as a project risk,
                Prob. Of occurrence -70% ( high) and
                Impact-2 (critical)
To mitigate this risk, project management must develop a
    strategy for
reducing turnover.
Among the possible steps to be taken --
   Meet with current staff to determine causes for turnover (e.g.,
    poor working conditions, low pay, and competitive job market).
   Mitigate those causes that are under our control before the project
    starts.
   Organize project teams so that information about each
    development activity is widely dispersed.
   Define documentation standards and establish mechanisms to be
    sure that documents are developed in a timely manner.
   Assign a backup staff member for every critical
    technologist.
2. Risk monitoring
   As the project proceeds, risk monitoring activities commence.
   The project manager monitors factors that may provide an
    indication of whether the risk is becoming more or less likely.

    In the case of high staff turnover, the following
    factors can be monitored:
   General attitude of team members based on project
    pressures.
   The degree to which the team has jelled.
   Interpersonal relationships among team members.
   Potential problems with compensation and benefits.
   The availability of jobs within the company and outside it.
   Also the project manager should monitor the
    effectiveness of risk mitigation steps.

   The project manager should monitor documents
    carefully to ensure that each can stand on its own
    and that each imparts information that would be
    necessary if a newcomer were forced to join the
    software team somewhere in the middle of the
    project.
3. Risk management
• Assumes that mitigation efforts have failed and that the risk

  has become a reality (a number of people announce that they
  are leaving)
• If the mitigation strategy has been followed, backup is

  available, information is documented, and knowledge has
  been dispersed across the team.
• Those individuals who are leaving are asked to stop all work

  and spend their last weeks in “knowledge transfer mode. This
  might include video-based knowledge capture, the
  development of “commentary documents,” and/or meeting
  with other team members who will remain on the project.
   The RMMM plan documents all work performed as
    part of risk analysis and are used by the project
    manager as part of the overall project plan.
   Some software teams do not develop a formal RMMM
    document. Rather, each risk is documented
    individually using a risk information sheet (RIS)
   Once RMMM has been documented and the project
    has begun, risk mitigation and monitoring steps
    commence. And if the risk becomes real then the
    project manager applies the management steps.
Risk ID: P02-4-32           Date : 5/9/02     Prob: 80%        Impact : High
Description :
Only 70 % of the software components scheduled for reuse will be integrated
   into the application. The remaining functionality will have to be custom
   developed.
Refinement/Context
Sub condition 1
 Certain reusable components were developed by a third party with no
   knowledge of internal design standards.
  Sub condition 2
 Certain reusable components have been implemented in a language
 that is not supported on the target environment.
Mitigation/Monitoring :
1. Contact third party to determine conformance with design standards.
2. Check to determine if language support can be acquired.
Management Plan :
• RE computed to be $20,200. Allocate this amount

  within project cost.
• Develop revised schedule assuming 18 additional

  components will have to be custom built.
• Allocate staff accordingly.

Current Status :
6/12/2010 : Mitigation steps initiated.

Contenu connexe

Tendances

Risk management in software engineering
Risk management in software engineeringRisk management in software engineering
Risk management in software engineeringdeep sharma
 
Quantitative Project Risk Analysis
Quantitative Project Risk AnalysisQuantitative Project Risk Analysis
Quantitative Project Risk AnalysisIntaver Insititute
 
Risk Assessment: Creating a Risk Matrix
Risk Assessment: Creating a Risk MatrixRisk Assessment: Creating a Risk Matrix
Risk Assessment: Creating a Risk MatrixEtQ, Inc.
 
Risk Analysis PowerPoint Presentation Slides
Risk Analysis PowerPoint Presentation Slides Risk Analysis PowerPoint Presentation Slides
Risk Analysis PowerPoint Presentation Slides SlideTeam
 
Risk management(software engineering)
Risk management(software engineering)Risk management(software engineering)
Risk management(software engineering)Priya Tomar
 
Risk assessment techniques a critical success factor
Risk assessment techniques a critical success factorRisk assessment techniques a critical success factor
Risk assessment techniques a critical success factorPECB
 
Risk analysis and management
Risk analysis and managementRisk analysis and management
Risk analysis and managementgnitu
 
Software Engineering (Risk Management)
Software Engineering (Risk Management)Software Engineering (Risk Management)
Software Engineering (Risk Management)ShudipPal
 
Unit 8-risk manaegement (1) -
Unit 8-risk manaegement (1) - Unit 8-risk manaegement (1) -
Unit 8-risk manaegement (1) - Shashi Kumar
 
Qualitative & Quantitative Analysis
Qualitative & Quantitative AnalysisQualitative & Quantitative Analysis
Qualitative & Quantitative AnalysisAlin Veronika
 
Pressman ch-25-risk-management
Pressman ch-25-risk-managementPressman ch-25-risk-management
Pressman ch-25-risk-managementzeeshanwrch
 
Risk Assessment PowerPoint Presentation Slides
Risk Assessment PowerPoint Presentation Slides Risk Assessment PowerPoint Presentation Slides
Risk Assessment PowerPoint Presentation Slides SlideTeam
 
Step by step guide on project risk management
Step by step guide on project risk managementStep by step guide on project risk management
Step by step guide on project risk managementPMC Mentor
 
Qualitative risk analysis
Qualitative risk analysisQualitative risk analysis
Qualitative risk analysissonali talkar
 

Tendances (20)

Risk Analysis
Risk AnalysisRisk Analysis
Risk Analysis
 
Risk management in software engineering
Risk management in software engineeringRisk management in software engineering
Risk management in software engineering
 
Risk Management by Roger Pressman
Risk Management by Roger PressmanRisk Management by Roger Pressman
Risk Management by Roger Pressman
 
Quantitative Project Risk Analysis
Quantitative Project Risk AnalysisQuantitative Project Risk Analysis
Quantitative Project Risk Analysis
 
Risk Assessment: Creating a Risk Matrix
Risk Assessment: Creating a Risk MatrixRisk Assessment: Creating a Risk Matrix
Risk Assessment: Creating a Risk Matrix
 
Risk Analysis PowerPoint Presentation Slides
Risk Analysis PowerPoint Presentation Slides Risk Analysis PowerPoint Presentation Slides
Risk Analysis PowerPoint Presentation Slides
 
Risk management(software engineering)
Risk management(software engineering)Risk management(software engineering)
Risk management(software engineering)
 
Risk Management
Risk ManagementRisk Management
Risk Management
 
Risk assessment techniques a critical success factor
Risk assessment techniques a critical success factorRisk assessment techniques a critical success factor
Risk assessment techniques a critical success factor
 
Risk analysis and management
Risk analysis and managementRisk analysis and management
Risk analysis and management
 
Software Engineering (Risk Management)
Software Engineering (Risk Management)Software Engineering (Risk Management)
Software Engineering (Risk Management)
 
Unit 8-risk manaegement (1) -
Unit 8-risk manaegement (1) - Unit 8-risk manaegement (1) -
Unit 8-risk manaegement (1) -
 
Qualitative & Quantitative Analysis
Qualitative & Quantitative AnalysisQualitative & Quantitative Analysis
Qualitative & Quantitative Analysis
 
Risk management
Risk managementRisk management
Risk management
 
Pressman ch-25-risk-management
Pressman ch-25-risk-managementPressman ch-25-risk-management
Pressman ch-25-risk-management
 
Risk assessment tools and techniques
Risk assessment tools and techniquesRisk assessment tools and techniques
Risk assessment tools and techniques
 
Risk Assessment PowerPoint Presentation Slides
Risk Assessment PowerPoint Presentation Slides Risk Assessment PowerPoint Presentation Slides
Risk Assessment PowerPoint Presentation Slides
 
Step by step guide on project risk management
Step by step guide on project risk managementStep by step guide on project risk management
Step by step guide on project risk management
 
Risk management
Risk managementRisk management
Risk management
 
Qualitative risk analysis
Qualitative risk analysisQualitative risk analysis
Qualitative risk analysis
 

En vedette

Software Risk Analysis
Software Risk AnalysisSoftware Risk Analysis
Software Risk AnalysisBrett Leonard
 
Powerpoint Risk Assessment
Powerpoint Risk AssessmentPowerpoint Risk Assessment
Powerpoint Risk AssessmentSteve Bishop
 
Hazard Identification, Risk Assessment and Risk Control (HIRARC) Malay version
Hazard Identification, Risk Assessment and Risk Control (HIRARC) Malay versionHazard Identification, Risk Assessment and Risk Control (HIRARC) Malay version
Hazard Identification, Risk Assessment and Risk Control (HIRARC) Malay versionNorrazman Zaiha Zainol
 
OHSAS Hazard identification & Risk assessment
OHSAS Hazard identification & Risk assessmentOHSAS Hazard identification & Risk assessment
OHSAS Hazard identification & Risk assessmentTechnoSysCon
 
Risk assessment presentation
Risk assessment presentationRisk assessment presentation
Risk assessment presentationmmagario
 
Risk assessment principles and guidelines
Risk assessment principles and guidelinesRisk assessment principles and guidelines
Risk assessment principles and guidelinesHaris Tahir
 
Project Risk Management
Project Risk ManagementProject Risk Management
Project Risk ManagementMarkos Mulat G
 
Applying Robotic Process Automation in Banking: Innovations in Finance and Risk
Applying Robotic Process Automation in Banking: Innovations in Finance and RiskApplying Robotic Process Automation in Banking: Innovations in Finance and Risk
Applying Robotic Process Automation in Banking: Innovations in Finance and Riskaccenture
 

En vedette (10)

Software Risk Analysis
Software Risk AnalysisSoftware Risk Analysis
Software Risk Analysis
 
Powerpoint Risk Assessment
Powerpoint Risk AssessmentPowerpoint Risk Assessment
Powerpoint Risk Assessment
 
Bond
BondBond
Bond
 
Hazard Identification, Risk Assessment and Risk Control (HIRARC) Malay version
Hazard Identification, Risk Assessment and Risk Control (HIRARC) Malay versionHazard Identification, Risk Assessment and Risk Control (HIRARC) Malay version
Hazard Identification, Risk Assessment and Risk Control (HIRARC) Malay version
 
OHSAS Hazard identification & Risk assessment
OHSAS Hazard identification & Risk assessmentOHSAS Hazard identification & Risk assessment
OHSAS Hazard identification & Risk assessment
 
Risk assessment presentation
Risk assessment presentationRisk assessment presentation
Risk assessment presentation
 
Risk assessment principles and guidelines
Risk assessment principles and guidelinesRisk assessment principles and guidelines
Risk assessment principles and guidelines
 
Project Risk Management
Project Risk ManagementProject Risk Management
Project Risk Management
 
Applying Robotic Process Automation in Banking: Innovations in Finance and Risk
Applying Robotic Process Automation in Banking: Innovations in Finance and RiskApplying Robotic Process Automation in Banking: Innovations in Finance and Risk
Applying Robotic Process Automation in Banking: Innovations in Finance and Risk
 
Project risk analysis
Project risk analysisProject risk analysis
Project risk analysis
 

Similaire à Risk analysis

riskanalysis-120305101118-phpapp02.pdf
riskanalysis-120305101118-phpapp02.pdfriskanalysis-120305101118-phpapp02.pdf
riskanalysis-120305101118-phpapp02.pdfWilliamTom9
 
OOSE-PRESENTATION.pptx
OOSE-PRESENTATION.pptxOOSE-PRESENTATION.pptx
OOSE-PRESENTATION.pptxRanjitKdk
 
pressman-ch-25-risk-management.ppt
pressman-ch-25-risk-management.pptpressman-ch-25-risk-management.ppt
pressman-ch-25-risk-management.pptMuhammadKashif703372
 
Project Management C7 -risk_management
Project Management C7  -risk_managementProject Management C7  -risk_management
Project Management C7 -risk_managementIzah Asmadi
 
risk management
risk managementrisk management
risk managementArti Maggo
 
Risk-Management-05012023-025512pm.ppt
Risk-Management-05012023-025512pm.pptRisk-Management-05012023-025512pm.ppt
Risk-Management-05012023-025512pm.pptYasirShaikh34
 
Software Project Risks Management (1).pdf
Software Project Risks Management (1).pdfSoftware Project Risks Management (1).pdf
Software Project Risks Management (1).pdfShivareddyGangam
 
risk-management-121021125051-phpapp02 (1).pdf
risk-management-121021125051-phpapp02 (1).pdfrisk-management-121021125051-phpapp02 (1).pdf
risk-management-121021125051-phpapp02 (1).pdfPriyanshTan
 
Project Name Risk Management PlanVersion 1.0 Error! Unkno.docx
Project Name Risk Management PlanVersion 1.0 Error! Unkno.docxProject Name Risk Management PlanVersion 1.0 Error! Unkno.docx
Project Name Risk Management PlanVersion 1.0 Error! Unkno.docxwkyra78
 
Project Planning and Management.pptx
Project Planning and Management.pptxProject Planning and Management.pptx
Project Planning and Management.pptxvishnupriyapm4
 
D.Q1Information System and Enterprise Systems· Identify.docx
D.Q1Information System and Enterprise Systems· Identify.docxD.Q1Information System and Enterprise Systems· Identify.docx
D.Q1Information System and Enterprise Systems· Identify.docxtheodorelove43763
 
10.9 STORE-DRIVEN FORECASTS. The Home Depot is a lead.docx
10.9  STORE-DRIVEN FORECASTS. The Home Depot is a lead.docx10.9  STORE-DRIVEN FORECASTS. The Home Depot is a lead.docx
10.9 STORE-DRIVEN FORECASTS. The Home Depot is a lead.docxhyacinthshackley2629
 

Similaire à Risk analysis (20)

riskanalysis-120305101118-phpapp02.pdf
riskanalysis-120305101118-phpapp02.pdfriskanalysis-120305101118-phpapp02.pdf
riskanalysis-120305101118-phpapp02.pdf
 
OOSE-PRESENTATION.pptx
OOSE-PRESENTATION.pptxOOSE-PRESENTATION.pptx
OOSE-PRESENTATION.pptx
 
Risk Management
Risk ManagementRisk Management
Risk Management
 
Project risk analysis
Project risk analysisProject risk analysis
Project risk analysis
 
Risk
RiskRisk
Risk
 
pressman-ch-25-risk-management.ppt
pressman-ch-25-risk-management.pptpressman-ch-25-risk-management.ppt
pressman-ch-25-risk-management.ppt
 
Project Management C7 -risk_management
Project Management C7  -risk_managementProject Management C7  -risk_management
Project Management C7 -risk_management
 
risk management
risk managementrisk management
risk management
 
RMMM
RMMMRMMM
RMMM
 
lec6.ppt
lec6.pptlec6.ppt
lec6.ppt
 
Risk-Management-05012023-025512pm.ppt
Risk-Management-05012023-025512pm.pptRisk-Management-05012023-025512pm.ppt
Risk-Management-05012023-025512pm.ppt
 
Software Project Risks Management (1).pdf
Software Project Risks Management (1).pdfSoftware Project Risks Management (1).pdf
Software Project Risks Management (1).pdf
 
risk-management-121021125051-phpapp02 (1).pdf
risk-management-121021125051-phpapp02 (1).pdfrisk-management-121021125051-phpapp02 (1).pdf
risk-management-121021125051-phpapp02 (1).pdf
 
Project Name Risk Management PlanVersion 1.0 Error! Unkno.docx
Project Name Risk Management PlanVersion 1.0 Error! Unkno.docxProject Name Risk Management PlanVersion 1.0 Error! Unkno.docx
Project Name Risk Management PlanVersion 1.0 Error! Unkno.docx
 
Session 18 -2 PMP 4th edition
Session 18 -2  PMP 4th editionSession 18 -2  PMP 4th edition
Session 18 -2 PMP 4th edition
 
Project Planning and Management.pptx
Project Planning and Management.pptxProject Planning and Management.pptx
Project Planning and Management.pptx
 
Project Risk Management
Project Risk ManagementProject Risk Management
Project Risk Management
 
D.Q1Information System and Enterprise Systems· Identify.docx
D.Q1Information System and Enterprise Systems· Identify.docxD.Q1Information System and Enterprise Systems· Identify.docx
D.Q1Information System and Enterprise Systems· Identify.docx
 
Session 10 gdas pmp study group presentation
Session 10   gdas pmp study group presentationSession 10   gdas pmp study group presentation
Session 10 gdas pmp study group presentation
 
10.9 STORE-DRIVEN FORECASTS. The Home Depot is a lead.docx
10.9  STORE-DRIVEN FORECASTS. The Home Depot is a lead.docx10.9  STORE-DRIVEN FORECASTS. The Home Depot is a lead.docx
10.9 STORE-DRIVEN FORECASTS. The Home Depot is a lead.docx
 

Plus de saurabhshertukde (19)

Revision sql te it new syllabus
Revision sql te it new syllabusRevision sql te it new syllabus
Revision sql te it new syllabus
 
Oodbms ch 20
Oodbms ch 20Oodbms ch 20
Oodbms ch 20
 
Introduction er & eer
Introduction er & eerIntroduction er & eer
Introduction er & eer
 
Introduction er & eer
Introduction er &  eerIntroduction er &  eer
Introduction er & eer
 
Integrity & security
Integrity & securityIntegrity & security
Integrity & security
 
Er model
Er modelEr model
Er model
 
Er & eer to relational mapping
Er & eer to relational mappingEr & eer to relational mapping
Er & eer to relational mapping
 
Eer case study
Eer case studyEer case study
Eer case study
 
Chapter 2
Chapter 2Chapter 2
Chapter 2
 
Chapter 1
Chapter 1Chapter 1
Chapter 1
 
Chapter 9
Chapter 9Chapter 9
Chapter 9
 
J2 ee archi
J2 ee archiJ2 ee archi
J2 ee archi
 
J2 ee architecture
J2 ee architectureJ2 ee architecture
J2 ee architecture
 
Software project-scheduling
Software project-schedulingSoftware project-scheduling
Software project-scheduling
 
Softwareproject planning
Softwareproject planningSoftwareproject planning
Softwareproject planning
 
Pressman ch-3-prescriptive-process-models
Pressman ch-3-prescriptive-process-modelsPressman ch-3-prescriptive-process-models
Pressman ch-3-prescriptive-process-models
 
Design concepts and principles
Design concepts and principlesDesign concepts and principles
Design concepts and principles
 
Analysis modelling
Analysis modellingAnalysis modelling
Analysis modelling
 
Analysis concepts and principles
Analysis concepts and principlesAnalysis concepts and principles
Analysis concepts and principles
 

Dernier

UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfDianaGray10
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarPrecisely
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxMatsuo Lab
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024D Cloud Solutions
 
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdfIaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdfDaniel Santiago Silva Capera
 
Cybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptxCybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptxGDSC PJATK
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1DianaGray10
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfJamie (Taka) Wang
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8DianaGray10
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URLRuncy Oommen
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7DianaGray10
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAshyamraj55
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...DianaGray10
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdfPedro Manuel
 

Dernier (20)

UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity Webinar
 
Introduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptxIntroduction to Matsuo Laboratory (ENG).pptx
Introduction to Matsuo Laboratory (ENG).pptx
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024
 
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdfIaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
IaC & GitOps in a Nutshell - a FridayInANuthshell Episode.pdf
 
Cybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptxCybersecurity Workshop #1.pptx
Cybersecurity Workshop #1.pptx
 
Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1Secure your environment with UiPath and CyberArk technologies - Session 1
Secure your environment with UiPath and CyberArk technologies - Session 1
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URL
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7
 
20150722 - AGV
20150722 - AGV20150722 - AGV
20150722 - AGV
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
Connector Corner: Extending LLM automation use cases with UiPath GenAI connec...
 
Nanopower In Semiconductor Industry.pdf
Nanopower  In Semiconductor Industry.pdfNanopower  In Semiconductor Industry.pdf
Nanopower In Semiconductor Industry.pdf
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 

Risk analysis

  • 2. Risks are potential problem/uncertainty that might affect the successful completion of a software project.  Risk analysis and management are intended to help a software team understand and manage uncertainty during the development process.  The work product is called a Risk Mitigation, Monitoring, and Management Plan (RMMM).
  • 3.  Two risk Strategies : 1. Reactive strategy Software team does nothing till the risk becomes real. 2. Proactive strategy Risk management begins long before technical work starts. Risks are identified and prioritized by importance. Then team builds a plan to avoid risks if they can or minimize their probability of occurrence or establish plan if risks become real.
  • 4.  Categories of risks 1. Project risks ◦ Threatens the project plan. ◦ If project risk becomes real, it is likely project schedule will slip and the costs will increase ◦ Identifies problems related to budgetary, schedule , personnel and resource 2. Technical risk o Threatens the quality of the software to be produced. o Identifies problems related to design, implementation, maintenance etc
  • 5. 3.Business risk • Threatens the viability of the software to be built. • Eg of business risk 4. Building an excellent product that no one wants. 5. Building a product that no longer fits into the overall business strategy. 6. Building a product that the sales force do not how to sell. 7. Change of management 8. Losing budgetary
  • 6.  Steps for risk analysis 2. Risk Identification • Lists the risks associated with a specific project. • Use a risk item checklist to identify risks Risk item check list – A set of questions relevant to each risk. A project manager attains a feeling of staffing risk by answering the following set questions--- 8. Are enough people available ? 9. Are the best people available ? 10.Will the project team members be working full time / part time on the project ? 11.Have the staff members received necessary training? No. of negative responses to the questions ∝ degree to which the project is at a staffing risk
  • 7. 2. Risk projection • Also called risk estimation. • Rates each risk in 2 ways : 4. Find the probability of occurrence of each risk. 5. Find the impact of the problems associated with each risk. Steps 1 : Prepare a risk table. a) Lists all risks identified in the first column. b) Category of the risk is identified in the second column. PS – project size risk. TE – Technical risk. BU – Business risk.
  • 8. c) Probability of occurrence is entered in the third column. Individual team members are polled for their estimates in a round robin fashion until a single consensus is obtained. d) Impact of each risk on the 4 risk components is assessed . 4 risk components are 1. Performance If the risk becomes real will the requirements be met and will the product be fit for its intended use? 2. Cost If the risk becomes real will the project budget be maintained? 3. Support If the risk becomes real will the resultant software be easy to correct , adapt and enhance?
  • 9. 4. Schedule Will the project schedule be maintained and the product will be delivered on time if the risk becomes real? The impact of each risk on the 4 components can be categorized as 1- Catastrophic 2- Critical 3- Marginal 4- Negligible The values are averaged to determine an overall impact value.
  • 10. Table prior to sorting
  • 11. Next the table is sorted by high probability and high impact. • Project manager defines a cut off line implying only risks above the line will be managed. • The column labeled RMMM contains a pointer into a Risk Mitigation Monitoring and Management Plan(A collection of risk information sheets developed for all risks that lie above the cutoff line)
  • 12. Steps 2 : Assessing the risk impact . a) Estimate the cost of each risk in the table. • How to estimate the cost of each risk ? Eg : Assume that the software team defines a project risk in the following manner: Risk identification. Only 70 percent of the software components scheduled for reuse will, in fact, be integrated into the application. The remaining functionality will have to be custom developed. Risk probability. 80% (likely). Risk impact. 60 reusable software components were planned. If only 70 percent can be used, 18 components would have to be developed from scratch (in addition to other custom software that has been scheduled for development). Since the average component is 100 LOC and local data indicate that the software engineering cost for each LOC is $14.00, the overall cost (impact) to develop the components would be 18 x 100 x 14 = $25,200.
  • 13. b) Calculate the risk exposure foe each risk in the table ---- Risk exposure. RE = Prob. Of occurrence x cost of risk =0.80 x 25,200 ~ $20,200. c) Calculate the total exposure for all risks(above the cutoff line) The total risk exposure provides a means for adjusting the final cost estimates for a project. If RE is greater than 50 % of the project cost , the viability of the project must be evaluated
  • 14. 3. Risk Refinement • During early stages of project planning, a risk may be stated quite generally. • As time passes and more is learned about the project and the risk, it may be possible to refine the risk. • One way to do this is to represent the risk in condition- transition-consequence (CTC) • Given that <condition> then there is concern that (possibly) <consequence>.
  • 15. Using the CTC format for the reuse risk ---- • Given that all reusable software components must conform to specific design standards and that some do not conform, then there is concern that (possibly) only 70 % of the planned reusable modules may actually be integrated into the as-built system, resulting in the need to custom engineer the remaining 30 % of components. • This general condition can be refined in the following manner: Sub condition 1 Certain reusable components were developed by a third party with no knowledge of internal design standards. Sub condition 2 Certain reusable components have been implemented in a language that is not supported on the target environment.
  • 16. 4. Risk Mitigation Monitoring and Management All the risk analysis activities presented so far have single goal i.e to assist the project team in developing a strategy to deal with risk. An effective strategy is-- 6. Risk Mitigation (avoidance) For example, Assume Risk -High staff turnover is noted as a project risk, Prob. Of occurrence -70% ( high) and Impact-2 (critical)
  • 17. To mitigate this risk, project management must develop a strategy for reducing turnover. Among the possible steps to be taken --  Meet with current staff to determine causes for turnover (e.g., poor working conditions, low pay, and competitive job market).  Mitigate those causes that are under our control before the project starts.  Organize project teams so that information about each development activity is widely dispersed.  Define documentation standards and establish mechanisms to be sure that documents are developed in a timely manner.  Assign a backup staff member for every critical technologist.
  • 18. 2. Risk monitoring  As the project proceeds, risk monitoring activities commence.  The project manager monitors factors that may provide an indication of whether the risk is becoming more or less likely. In the case of high staff turnover, the following factors can be monitored:  General attitude of team members based on project pressures.  The degree to which the team has jelled.  Interpersonal relationships among team members.  Potential problems with compensation and benefits.  The availability of jobs within the company and outside it.
  • 19. Also the project manager should monitor the effectiveness of risk mitigation steps.  The project manager should monitor documents carefully to ensure that each can stand on its own and that each imparts information that would be necessary if a newcomer were forced to join the software team somewhere in the middle of the project.
  • 20. 3. Risk management • Assumes that mitigation efforts have failed and that the risk has become a reality (a number of people announce that they are leaving) • If the mitigation strategy has been followed, backup is available, information is documented, and knowledge has been dispersed across the team. • Those individuals who are leaving are asked to stop all work and spend their last weeks in “knowledge transfer mode. This might include video-based knowledge capture, the development of “commentary documents,” and/or meeting with other team members who will remain on the project.
  • 21. The RMMM plan documents all work performed as part of risk analysis and are used by the project manager as part of the overall project plan.  Some software teams do not develop a formal RMMM document. Rather, each risk is documented individually using a risk information sheet (RIS)  Once RMMM has been documented and the project has begun, risk mitigation and monitoring steps commence. And if the risk becomes real then the project manager applies the management steps.
  • 22. Risk ID: P02-4-32 Date : 5/9/02 Prob: 80% Impact : High Description : Only 70 % of the software components scheduled for reuse will be integrated into the application. The remaining functionality will have to be custom developed. Refinement/Context Sub condition 1 Certain reusable components were developed by a third party with no knowledge of internal design standards. Sub condition 2 Certain reusable components have been implemented in a language that is not supported on the target environment. Mitigation/Monitoring : 1. Contact third party to determine conformance with design standards. 2. Check to determine if language support can be acquired.
  • 23. Management Plan : • RE computed to be $20,200. Allocate this amount within project cost. • Develop revised schedule assuming 18 additional components will have to be custom built. • Allocate staff accordingly. Current Status : 6/12/2010 : Mitigation steps initiated.