Agile risk management - Enterprise agility

24
ADVANCED AGILE RISK MANAGEMENT 3 Points of Risk Management in Agile work

Transcript of Agile risk management - Enterprise agility

Page 1: Agile risk management - Enterprise agility

ADVANCED AGILE RISK

MANAGEMENT

3 Points of Risk Management in Agile work

Page 2: Agile risk management - Enterprise agility

What is RISK?

Risk Noun 1. a situation

involving exposure to danger.

Biggest Project Risks Deliver the Wrong

Thing Deliver the Right

Thing Too Late Deliver something

that does not work.

Page 3: Agile risk management - Enterprise agility

Being Agile Reduces Risk

Incremental Delivery of Working

ProductsCustomer Demos

Fail FastValue PrioritizedLoosely Coupled

ModulesDistributed

Decision Making

Deliver the Wrong Thing

Deliver the Right Thing Too Late

Deliver something that does not work.

Page 4: Agile risk management - Enterprise agility

Identify

Evaluate

PrioritizeRespond

Track

Risk Management

Page 5: Agile risk management - Enterprise agility

Probability/Impact Risk Statement

Some event may occur which may result in some consequence.

It is only a risk if you cannot PROVE it. Difference between a risk and

assumption An assumption you believe has a 100%

probably Positive Risk

Risk Language

Page 6: Agile risk management - Enterprise agility

Focus on the important Make Risk Visible Involve Everyone Make It Living Make it FAST

Principles

Page 7: Agile risk management - Enterprise agility

Find the risks

Identification

Page 8: Agile risk management - Enterprise agility

Chartering Story mapping Planning Retrospectives

When to do Identification

Page 9: Agile risk management - Enterprise agility

An assumption is a thing or action that is accepted as true or as certain to happen.

Assumptions only valid if you CANNOT prove otherwise

Chartering, Story Mapping, Planning What assumptions are you making? Include these in the following analysies

Assumption Analysis

Page 10: Agile risk management - Enterprise agility

SWOT

Strength Weakness

Opportunity

Threat

Internal/External Good Questions Perspectives: Marketing,

Sales, Customer, Shareholder

Quality Facilitation Personality types Risks Oversimplification

Page 11: Agile risk management - Enterprise agility

InternalQuestions

Strengths Weaknesses What makes you better than… What do actions do you do

well What do others say you do

well Why do people use/purchase

your product/service What advantages do you have What can you do that no one

else can do

What could you improve What do you doo poorly What should you avoid What do others say you do

poorly What can your competition

do that you cannot Where have you

historically done poorly

Page 12: Agile risk management - Enterprise agility

ExternalQuestions

Opportunities Threats What opportunities

face you What trends are you

aware of in your market

What changes in: Technology, government policy, social patterns are you able to exploit

What obstacles do you face Who might cause you

problems now or in the future?

What is your competition doing well that gives them an advantage over you

What technology, government, social events or patterns could harm you

Page 13: Agile risk management - Enterprise agility

Ishikawa

Root Cause(s) Defect

Machine Method Materia

l

People Environments

Measurement

Page 14: Agile risk management - Enterprise agility

ReverseIshikawa

Feature

Machine Method Materia

l

People Environments

Measurement

Page 15: Agile risk management - Enterprise agility

Identify

Assess

PrioritizeRespond

Track

Risk Management

Page 16: Agile risk management - Enterprise agility

Define

Probability Impact 1 = 0 – 10% 2 = 11 – 20% 3 = 21 – 50% 4 = 51 – 75% 5 = 75 – 100%

Or something like that you decide

How will you determine impact?

Cash? Delay? Other? Quantify the impact

Page 17: Agile risk management - Enterprise agility

Risk Probability1-5

Impact1-5

Risk Rating(P*I)1-25

The one developer who knows Cobol might leave

1 5 5

Bill HB-22345 includes language that may reduce our ability to sell this product

4 2 8

Our vendor does not follow an agile approach and may not be able to deliver late arriving requirements

3 5 15

Simple Analysis

Page 18: Agile risk management - Enterprise agility

Define

Probability Impact 1 = 0 – 10% 2 = 11 – 20% 3 = 21 – 50% 4 = 51 – 75% 5 = 75 – 100%

Or something like that you decide

How will you determine impact?

Cash? Delay? Other? Quantify the impact

Page 19: Agile risk management - Enterprise agility

Risk Probability1-5

Impact1-5

Risk Rating(P*I)1-25

The one developer who knows Cobol might leave

1 5 5

Bill HB-22345 includes language that may reduce our ability to sell this product

4 2 8

Our vendor does not follow an agile approach and may not be able to deliver late arriving requirements

3 5 15

Simple Analysis

Page 20: Agile risk management - Enterprise agility

Assessment

5 5 10 15 20 25

4 4 8 12 16 20

3 3 6 9 12 15

2 2 4 6 8 10

1 1 2 3 4 5

1 2 3 4 5

Prob

abilit

y

Impact

Page 21: Agile risk management - Enterprise agility

Identify

Assess

PrioritizeRespond

Track

Prioritize

Page 22: Agile risk management - Enterprise agility

Identify

Assess

PrioritizeRespond

Track

Respond

Page 23: Agile risk management - Enterprise agility

Identify

Assess

PrioritizeRespond

Track

Track

Page 24: Agile risk management - Enterprise agility

Summary