Risk Management

Июль 21, 2022

Содержание

2. Where are we? 1. Introduction. Scope of Project 2. Organizational Influence on Project Management 3. Project
3. Outline of talk What is Risk? Risk Identification: Threshold of Success Risk Management Plan Monitoring and
4. Outcomes Understand the key parts of the Risk Management Plan Know how to identify the key
5. What is Risk? A risk is a potential future harm that may arise from some present
6. What is Risk? There are a very few projects with no risk Software projects are fraught
7. What is Risk? Risk is the result of making decisions Every decision has two outputs, a
8. PEAK decision making process
9. PEAK decision making process (P) Problem: What is the issue to be resolved or the problem
10. Key of Risk Management Risk Identification Risk Prioritization Risk Mitigation Also: Risk Analysis – Take some
11. Key of Risk Management Capability Maturity Model Integration of SEI (Software Engineering Institute) (RSKM – Risk
12. Adult games A team is put together to build some software. Neither the clients nor the
13. Threshold of Success Defining and committing to a clear picture of success establishes the common ground
14. Threshold of Success Clearly identifies what the project must minimally do to make the customer satisfied
15. Threshold of Success A good Threshold of Success is made up of about 3-4 SMART goals
16. Threshold of Success Building a Threshold of Success The easiest way to create a Threshold of
17. Threshold of Success The threshold of success for my current project might look something like this.
18. Threshold of Success ToS statement:s We MUST do X or have shown that our product has
19. As part of a larger, comprehensive project plan, the risk management plan outlines the response that
20. Five main risk impact areas in Software Development: New, unproven technologies User and functional requirements Application
21. New, unproven technologies. The majority of software projects entail the use of new technologies. Training and
22. User and functional requirements. Software requirements capture all user needs with respect to the software system
23. Application and system architecture. Taking the wrong direction with a platform, component, or architecture can have
24. Performance. It’s important to ensure that any risk management plan encompasses user and partner expectations on
25. Organizational. Organizational problems may have adverse effects on project outcomes. Project management must plan for efficient
26. Writing Risk Statements
27. Writing Risk Statements
28. Writing Risk Statements
29. Writing Risk Statements
30. Lack of executive sponsorship (maybe because of change in the Administration); time delays, frustrations, credibility, and
31. Risk classification
32. Risk prioritization Probability Very Improbable Improbable Probable Frequent Impact Negligible Marginal Critical Catastrophic Numerical Value Risk
34. Table of risks
35. Key Ideas for Risk Management:
36. Risk management includes the following tasks: Identify risks and their triggers Classify and prioritize all risks
37. Risk mitigation Evaluation Project Decisions gives these activities Defining a Threshold of Success Identifying risks Formulating
38. Summary: A work team identifying risks needs to agree on an end-point against which to identify
40. Скачать презентацию

Слайд 2

Where are we?
1. Introduction. Scope of Project
2. Organizational Influence on Project

Management
3. Project Estimate
4. Software processes and artifacts
5. Risk Management

Слайд 3

Outline of talk
What is Risk?
Risk Identification: Threshold of Success
Risk Management Plan
Monitoring

and Mitigation of Risks

Слайд 4

Outcomes
Understand the key parts of the Risk Management Plan
Know how to

identify the key parts of the Threshold of Success (TOS) for a project.
Be able to write a TOS and begin writing Risks that can impact the TOS.
Have a clear understanding of what it means to mitigate a Risk.

Слайд 5

What is Risk?
A risk is a potential future harm that may

arise from some present action
(-> all risks have some probability rate of occurrence)

Слайд 6

What is Risk?
There are a very few projects with no risk
Software

projects are fraught with cost overrun and schedule delays
Risk management is an integral part of software project management

Слайд 7

What is Risk?
Risk is the result of making decisions
Every decision has

two outputs, a solutions and some risk
Risk is neither good or bad it just is, the impact might be good or bad
Risk has a probability and an impact
“A problem is a risk whose time has come”
All Risks should be based on a fact
Examples:
Good: A condition exists therefore this event might occur…
Bad: A condition might exist therefore …

Слайд 8

PEAK decision making process

Слайд 9

PEAK decision making process
(P) Problem: What is the issue to be resolved

or the problem to be solved? The problem statement should provide a clear representation of what needs to be solved.
(E) Experience: From prior events, what does the decision maker know or know how to do that might help with this problem? Has the decision maker seen or solved a problem like this one before? How appropriate and accurate is the decision maker's historical information?
(A) Assumptions: What information is accepted as fact without having evidence? What information about the problem does the decision maker abstract away because the information is not thought to be relevant to the solution?
(K) Knowledge: What conceptual understanding or factual basis can help the decision maker with the problem? What has the decision maker learned since last dealing with a problem like this? What facts does the decision maker have about the problem? What is the environment that surrounds this problem? For instance, when looking at military problems to be solved, soldiers might ask, "What is the current situation and terrain?“
http://www.informit.com/articles/article.aspx?p=1409781&seqNum=3

Слайд 10

Key of Risk Management
Risk Identification
Risk Prioritization
Risk Mitigation
Also:
Risk Analysis – Take

some time to consider risk
Risk Monitoring – Have a method to identify the status of risks as they change

Слайд 11

Key of Risk Management
Capability Maturity Model Integration of SEI (Software Engineering

Institute) (RSKM – Risk Management)

Слайд 12

Adult games
A team is put together to build some software.

Neither the clients nor the team talk about the objectives of the project other than building "some software". After a few months, something goes wrong or someone doesn't like what's happening so someone changes the rules. Before too long, one side or the other is upset that they can't win, somebody throws a fit, and goes home. Instead of summoning invisible armor, software projects change the rules by cutting features, adding more requirements, moving due dates, wasting resources, and things like that.

Слайд 13

Threshold of Success
Defining and committing to a clear picture of success

establishes the common ground rules for a project by making the basic project goals explicit. The technique is known as Threshold of Success.

Слайд 14

Threshold of Success
Clearly identifies what the project must minimally do to

make the customer satisfied
Establishes what are “must have” things versus “nice to have” items for the project
Provides a clear view of what must be done and therefore a clear view of what might impact what must be done
i.e., The risks of the project.

Слайд 15

Threshold of Success
A good Threshold of Success is made up of

about 3-4 SMART goals (no more than a few bullets on a single PowerPoint slide).
SMART is a mnemonic which stands for -
Specific
Measurable
Achievable
Relevant
Time bound.

Слайд 16

Threshold of Success
Building a Threshold of Success
The easiest way to create

a Threshold of Success is to first create a minimum picture of failure, then convert failure into success.
Example: Failure for my current project might look something like this.
Essential features are not ready by the end of the second quarter.
Team members are dissatisfied or bored with their jobs.
Newly hired team members don't feel like they're part of the team by March 31.
There isn't enough money to continue development after this fiscal year and we have to fire people.

Слайд 17

Threshold of Success
The threshold of success for my current project might

look something like this.
By the end of the second quarter, all "Must Have" features are implemented and pass acceptance tests with no known critical defects.
All team members give average score of 5 or better on a job satisfaction survey taken quarterly.
By March 31, the team has successfully executed at least three team building activities with all team members present.
Funds of at least $1 million are secured by December 31 to allow for future development without a reduction in team size.

Слайд 18

Threshold of Success
ToS statement:s
We MUST do X or have shown

that our product has met at least Y to reach our ToS.

Слайд 19

As part of a larger, comprehensive project plan, the risk management

plan outlines the response that will be taken for each risk—if it materializes

Risk management plan

Слайд 20

Five main risk impact areas in Software Development:
New, unproven technologies
User and

functional requirements
Application and system architecture
Performance
Organizational

Risk management plan

Слайд 21

New, unproven technologies. The majority of software projects entail the use of

new technologies. Training and knowledge are of critical importance, and the improper use of new technology most often leads directly to project failure.

Risk management plan

Слайд 22

User and functional requirements. Software requirements capture all user needs with respect

to the software system features, functions, and quality of service. Change in elemental requirements will likely propagate throughout the entire project, and modifications to user requirements might not translate to functional requirements.

Risk management plan

Слайд 23

Application and system architecture. Taking the wrong direction with a platform, component,

or architecture can have disastrous consequences. As with the technological risks, it is vital that the team includes experts who understand the architecture and have the capability to make sound design choices.

Risk management plan

Слайд 24

Performance. It’s important to ensure that any risk management plan encompasses user

and partner expectations on performance. Consideration must be given to benchmarks and threshold testing throughout the project to ensure that the work products are moving in the right direction.

Risk management plan

Слайд 25

Organizational. Organizational problems may have adverse effects on project outcomes. Project

management must plan for efficient execution of the project, and find a balance between the needs of the development team and the expectations of the customers.

Risk management plan

Слайд 26

Writing Risk Statements

Слайд 27

Writing Risk Statements

Слайд 28

Writing Risk Statements

Слайд 29

Writing Risk Statements

Слайд 30

Lack of executive sponsorship (maybe because of change in the Administration);

time delays, frustrations, credibility, and morale, and [a department cosponsoring the project] may pull out of [the project].
The majority of software-to-software interfaces are not defined & controlled; incomplete interfaces results in no benefits from [the project].
There has been inadequate schedule discipline (milestones, slippage, monitor progress, good project management) on this project; with no intervention the project will continue to slip & slide.

Example

Слайд 31

Risk classification

Слайд 32

Risk prioritization
Probability
Very Improbable
Improbable
Probable
Frequent
Impact
Negligible
Marginal
Critical
Catastrophic
Numerical Value
Risk Exposure (RE)= P * C

Слайд 33

Слайд 34

Table of risks

Слайд 35

Key Ideas for Risk Management:

Слайд 36

Risk management includes the following tasks:
Identify risks and their triggers
Classify and prioritize all

risks
Craft a plan that links each risk to a mitigation
Monitor for risk triggers during the project
Implement the mitigating action if any risk materializes
Communicate risk status throughout project

Risk mitigation

Слайд 37

Risk mitigation
Evaluation Project Decisions gives these activities
Defining a Threshold of Success
Identifying

risks
Formulating risk statements
Mitigating, tracking and controlling risk
Communicating about risk
Trading off resources to manage risk

Слайд 38

Summary:
A work team identifying risks needs to agree on an end-point

against which to identify and analyze the risks.
There needs to be a standard way of capturing (documenting) a risk.
Facilitators need practice to become comfortable writing risks in front of a group.
There are many ways for program management to support good risk identification:
Encourage documentation of risks privately at the working team level
Integrate risk identification and management into normal project management
Accept any risk identified into the repository – don’t “vet them out”
Acknowledge that the program’s decision-makers are the real “risk managers,” and have the decision-makers step up to the job

Risk Management

Содержание

Where are we?1. Introduction. Scope of Project2. Organizational Influence on Project

Outline of talkWhat is Risk?Risk Identification: Threshold of SuccessRisk Management PlanMonitoring

OutcomesUnderstand the key parts of the Risk Management PlanKnow how to

What is Risk?A risk is a potential future harm that may

What is Risk?There are a very few projects with no riskSoftware

What is Risk?Risk is the result of making decisionsEvery decision has

PEAK decision making process

PEAK decision making process(P) Problem: What is the issue to be resolved

Key of Risk ManagementRisk IdentificationRisk PrioritizationRisk MitigationAlso: Risk Analysis – Take

Key of Risk ManagementCapability Maturity Model Integration of SEI (Software Engineering

Adult games A team is put together to build some software.

Threshold of Success Defining and committing to a clear picture of success

Threshold of SuccessClearly identifies what the project must minimally do to

Threshold of Success A good Threshold of Success is made up of

Threshold of SuccessBuilding a Threshold of Success The easiest way to create

Threshold of SuccessThe threshold of success for my current project might

Threshold of SuccessToS statement:s We MUST do X or have shown

As part of a larger, comprehensive project plan, the risk management

Five main risk impact areas in Software Development:New, unproven technologiesUser and

New, unproven technologies. The majority of software projects entail the use of

User and functional requirements. Software requirements capture all user needs with respect

Application and system architecture. Taking the wrong direction with a platform, component,

Performance. It’s important to ensure that any risk management plan encompasses user

Organizational. Organizational problems may have adverse effects on project outcomes. Project

Writing Risk Statements

Writing Risk Statements

Writing Risk Statements

Writing Risk Statements

Lack of executive sponsorship (maybe because of change in the Administration);

Risk classification

Risk prioritizationProbability Very ImprobableImprobableProbableFrequentImpactNegligibleMarginalCriticalCatastrophicNumerical Value Risk Exposure (RE)= P * C

Table of risks

Key Ideas for Risk Management:

Risk management includes the following tasks: Identify risks and their triggersClassify and prioritize all

Risk mitigationEvaluation Project Decisions gives these activitiesDefining a Threshold of SuccessIdentifying

Summary:A work team identifying risks needs to agree on an end-point

Похожие презентации

Where are we?
1. Introduction. Scope of Project
2. Organizational Influence on Project

Outline of talk
What is Risk?
Risk Identification: Threshold of Success
Risk Management Plan
Monitoring

Outcomes
Understand the key parts of the Risk Management Plan
Know how to

What is Risk?
A risk is a potential future harm that may

What is Risk?
There are a very few projects with no risk
Software

What is Risk?
Risk is the result of making decisions
Every decision has

PEAK decision making process
(P) Problem: What is the issue to be resolved

Key of Risk Management
Risk Identification
Risk Prioritization
Risk Mitigation
Also:
Risk Analysis – Take

Key of Risk Management
Capability Maturity Model Integration of SEI (Software Engineering

Adult games
A team is put together to build some software.

Threshold of Success
Defining and committing to a clear picture of success

Threshold of Success
Clearly identifies what the project must minimally do to

Threshold of Success
A good Threshold of Success is made up of

Threshold of Success
Building a Threshold of Success
The easiest way to create

Threshold of Success
The threshold of success for my current project might

Threshold of Success
ToS statement:s
We MUST do X or have shown

Five main risk impact areas in Software Development:
New, unproven technologies
User and

Risk prioritization
Probability
Very Improbable
Improbable
Probable
Frequent
Impact
Negligible
Marginal
Critical
Catastrophic
Numerical Value
Risk Exposure (RE)= P * C

Risk management includes the following tasks:
Identify risks and their triggers
Classify and prioritize all

Risk mitigation
Evaluation Project Decisions gives these activities
Defining a Threshold of Success
Identifying

Summary:
A work team identifying risks needs to agree on an end-point