Professional Documents
Culture Documents
SEI Risk MGT Framework
SEI Risk MGT Framework
SEI Risk MGT Framework
Introduction
*The Definition of risk in software project?
Webster defines “risk” as “ the possibility
or injury”.
Risk in software project is defined as
exposure to harm and loss
*Why do we need risk management?
Risk management can help us to avoid
software disaster, rework and overkill.
Risk
Is characterized by is characterized by
Probability Loss
is defined by
Expectations
is valued by
Stakeholder
Riskit Method Processes
Risk Management Mandate
Output -> why, what, when and whom
Goal Review
Output -> explicit goal definitions
Risk Identification
Output ->A list of “raw” risks
Risk Analysis
Output ->Completed Riskit analysis graphs
and ranked risk scenarios
Riskit Method Processes
Risk Control Planning
Output->Selected risk controlling
actions
Risk Control
Output ->Reduced risks
Risk Monitoring
Output->Risk status information
Riskit Risk Management Cycle
Risk Mag mandate
Mandate Goal review
changes
changes goal
Utility Risk
loss Effect set
Differences of Two Methods
SEI focus on team member’s participation
SEI focus on the participation of suppliers and
customers
SEI method shares product vision
SEI method has open communication
SEI provides a continues risk management
Simulations