Torben Hoelgaard - Implementing Change - EuroSTAR 2011

Implementing change =

Methods + People + Processes

EuroSTAR 2011, Manchester, UK

Torben Hoelgaard

Torben Hoelgaard, B.Sc. in IT, Test and QA Consultant, CEO

Founded Software-Pro in 2008

Software-Pro is a Danish consultancy company. We assist our clients with testing and using knowledge from testing to implement change. Test Assessments, - Strategies, - Processes, - Methods, - Training, Coaching

Experience: 3 years of consulting in ATP, Saxo Bank and 18 other companies

4 years as VP of Corp. Quality Assurance at Saxotech

4 years as VP of Services at Saxotech

3 years as Nordic Sales Manager at Saxotech

3 years as Project Chief at Saxotech

7 years as Project Manager at Nordjyske

________

20+ years as Change Agent

Key Points

1. Core aspects of Change Management:

A. Methods + People + Processes

B. Organizational levels

C. Maturity

2. Involve all organizational levels

3. Metrics that fit various maturity levels

© S

oftw

are

-Pro

A: Methods + People + Processes

Methods / tools

People

Processes Input Process Output

B: Organizational levels

People come from different organizational levels:

Strategic

Tactic

Operational

Each level speaks their own language

Express your arguments and metrics in their language

CEO

Manager

Developers

Manager

Analysts Testers

…

…

Organizational languages

Strategic Money, Customer Satisfaction

Traffic lights, Predictability

Tactic Plans, Reports, Budgets

Processes, Release Mgnt.

Operational Test Techniques, Tools

Test Types, Use Cases

CEO

Manager

Developers

Manager

Analysts Testers

…

…

C: Maturity

Maturity level

CMM / CMMI

TMM / TMMI

SMMM

Remember Level 2!

Ref. wikimedia.org

http://upload.wikimedia.org/wikipedia/en/e/ec/Characteristics_of_Capability_Maturity_Model.svg

Combining it all…



C. Maturity

Methods and Processes can be more or less mature, so can People and Departments E.g.

The maturity level in Sales or Operations can be very different from Development

A person may be on a different maturity level than his/her Department

… into a Change Cube

© S

oftw

are

-Pro

Processes

People

Methods

Level 3

Level 2

Level 1

Strategic

Tactic

Operational

B Organizational

level

A M+P+P

C Maturity

Key Points




C. Maturity



© S

oftw

are

-Pro

Involving all organizational levels

CEO

YOU

Developers

Manager

Analysts Testers

…

…

Involve all organizational levels

… in what you say present, visualize, sell, convince…

… in who you listen to ask for their perspectives

ask how you can help them meet their goals

… in what you do Metrics, reports, decisions

Selecting, designing, training in templates

Methods, Tools, Process

Involving clients

CEO

Manager

Developers

Manager

Analysts Testers

…

…

CEO

Manager

Users

Manager

Users Users

…

…

Your organization Other organization

Key Points




C. Maturity



© S

oftw

are

-Pro

Metrics – Authentic examples

Fitting low maturity level and up W-model Process Metrics *

Customer reported defects *

Fitting medium maturity level Release Metrics

Test Coverage

Fitting any maturity level TMM metrics *

Customer Survey *

* Examples taken from the

same client, to document

how changes lead to

improved maturity and

customer satisfaction

W-model

5. Write System Design

3. Write Technical

Requirements

9. Build, Debug & Rebuild

Software

11. Build, Debug & Rebuild System

7. Write

Code

6. Review SD and prepare Integration

Test

2. Review BR and prepare Acceptance

Test

1. Write Business

Requirements

13. Install

System

12. System

Test

15. Acceptance

Test

8. Unit Test and Review

Code

10. Integration

Test

4. Review TR and prepare System Test

Ver. 1.5. / DEC 2005 / T.Hoelgaard

14. Beta

Test

W-model Process Metrics - August 2006

W-model Process Metrics - August 2007

Customer reported defects


Fitting low maturity level and up W-model Process Metrics



Test Coverage

Fitting any maturity level TMM metrics

Customer Survey

Release Metrics – Dashboard

Test Coverage - Exercise

Case:

You have designed 50 test cases

You planned to execute 40 test cases

You actually managed to execute 30

What is your test coverage?

A: 80%

B: 75%

C: 60%

D: Don’t know

Test Coverage - Answer

If you planned for 40 tests and did 30, most Project Managers would think that your test coverage is 75% (which would be a pretty good test)

Right answer is D: Don’t know!

Test Coverage definition: The degree, in percent, to which a coverage item has been tested

Examples of Coverage Items: User Stories, requirements, interfaces, statements etc.

In this case we have no information about the number of tests needed to get 100% coverage E.g. if 200 tests were needed to get 100% coverage, and you did

30, the coverage would be 15% (which would be a pretty bad test)

Release Metrics – Test Progress


Fitting low maturity level and up W-model Process Metrics



Test Coverage

Fitting any maturity level TMM metrics

Customer Survey (not included in external copy)

TMM

22 Key Process Areas

=

22 Projects of Change!

Pick one or pick many

TMM – Starting point Feb 2005

Key Process Areas

0

10

20

30

40

50

60

70

80

90

100

Goa

ls

Plann

ing

Techni

ques

Enviro

nmen

t

Con

figM

gmt.

Incide

nts

Org

aniza

tion

Trainin

g

Inte

gratio

n

Non

-Fun

ctio

nal

Mon

itorin

g

Tools

Rev

iews

Risk

Mea

sure

men

t

Testa

bility

Dev

.Mat

.

Opt

imizat

ion

Know.M

gmt.

Qua

lity Con

trol

Cau

sal A

nl.

Preve

ntio

n

Perc

en

t

TMM – From Level 1 to 4 in 3 years

0

20

40

60

80

100

TMM Saxotech DK

Feb 2005 June 2006 March 2008

Summary: Any change is possible

- if there are solid logical arguments for it, and

- the Change Manager has experience in implementing change:

1. Using the Change Cube A. Methods + People + Processes


C. Maturity

2. Involving all organizational levels

3. Using the right metrics

© S

oftw

are

-Pro

Torben Hoelgaard - Implementing Change - EuroSTAR 2011

Technology

Transcript of Torben Hoelgaard - Implementing Change - EuroSTAR 2011