testing and lean principles eurostar 2010 · testing approach • built on values and principles in...

Copyright Karpinska & Nordström

Testing and lean principlesEurostar 2010

Beata Karpinska and Ingvar Nordström

1

Copyright Karpinska & NordströmCopyright Karpinska & Nordström

Who are we?

• Beata has a great deal of experience in testing

• Test Manager at 3L System

• Experiences as trainer in test and quality assurance

• Vice Chair SSTB, Swedish Software Testing Board (ISTQB)

• Ingvar has many years of experience in testing

• Technical Manager at Scania (Test improvements, methods).

• Chair of SSTB, Swedish Software Testing Board (ISTQB)

2


Cornerstones in Lean Thinking

• Define value seen from the customers point of view

• Continuous improvements

• Elimination of waste

• Respect for people

• Amplify learning

Lean is a Journey, not a Destination- Mary Poppendick

3


Lean and agile methods

Lean is a philosophy built on principlesLean thinking applied on entire organization

Lean

Agile

Scrum

Kanban XP

RUP Waterfall4


Be efficient by avoiding unnecessary things

Overprocessing

Idle time

Bad quality

Overproduction

Waiting

Inventory

Transport

5


Eliminate unnecessary movement

Waste:

• Lack of communication

• Late Handovers

• Slow start of execution without time for preparation

Go and see!Requirement

DevelopmentTest

Testing is not only top of an iceberg!

6


Avoid re-work!Wait as long as possible with the decision

RequirementsMore

understandingDesign

Test analysisTest

conditions

Product risks

Priority

Must Should Could Won't

Alternative:Exploratory testing

Test cases

7

MoSCoW


Avoid “inventory” wastes!

• Defects

• Unfinished preparation for testing

• The duplication of work

• Unnecessary features

• Usability issues

It’s not a bugIt’s a feature FAD = Function as

designed! Please train the user on how to use

the system! Bug no #3557

8


Too much documentation and output?

• Deliver only what is demanded!• Log tests!• Who is the user of the documentation?• Keep it short!

9


Testing Quadrants

10


Avoid extra processes!

11


Elimination of Waste

Identify core process

Identify usage of resource and its

qualifications

Redesign processto eliminate

waste

Less waste

Better QualityMore value for the customer

Challenge of implementing “lean”

12


Value stream - Map End-To-End-Flow

• How the process should be changed to move toward perfection

Review requirements

Design test casesChanged

designRework test

cases

Waste

Value 1 h

12 d

1 d

8 d

4 d

8 d

10 d

CooperateDesign test conditions

Design test cases

Waste

Value 7 h

3 d

6 d

2 d

4 d

1 d

10 d

1 h

13


” To win the war, choose your battles”

Goal 1 Goal 2 VisionGoal 3

14


Amplify learningTesting approach

• Built on Values and Principles in your company– No blame, forgiving

• Prototyping, early testing (review, evaluate)

• ”Right from me”

• Continuous improvements

• “Act” instead of “React”

• Early warning

• Go and See!

15


16

PRINCIPLESA way of thinking

RESULTContinuous

improvements

METHODSDevelop a way of doing

VALUESStable over time

PRINCIPLESA way of thinking

RESULTContinuous

improvements

METHODSDevelop a way of doing

VALUESStable over time

Values and principles


Amplify learningPrototyping, early testing

RequirementsMore

understandingDesign

Test analysisTest

conditions

Workshop

Exploratory testing

Test cases

Exploratory testing

17


18

Developer: early testing, early evaluation

“Right from me”

18

Module test


“Right from me”Put a stop to deviations

• Find bugs where they are created

• Solve serious problems before developing new things

• Prioritize to differentiate major from minor problems

• Remember: a bug report is one of the best foundation for improvements

19


2020

Input from testing:• Lessons learned

• Root cause analysis

• Customer complaints

• Support issues

Continuous improvements - Live example

• Improvement team = All involved

• The most important to succeed is that all are involved and focus on what can be done NOW

• Short meetings, ca 30 min

• Once a week, same time

• Use the whiteboard


Act vs. React

• When failures found in system testing, mitigation should be taken immediately

• ”Andon” – if serious failures discoverd, fix them, deliver service pack or new test release

• Do not wait for Summary Report!

• Prioritize so that expected serious failures can be found as early as possible.– Risk Based Testing

21


Early warning

• Act as a deputy customer

• Can test result reflect the quality after production?– Statistical connections between fault detection patterns/levels in

internal testing and product field quality.

• Is there a connection between support issues and test findings?

• In other words, can we use last test level as a measurement tool for field quality?

22


You have three job

• Your ordinary job

• Teach other

• Learn from other

–Go and see

23


Checklist for Lean Implementation

• Do we add value for the customer?

• Do we create more output than was asked for?

• Are we doing unnecessary tasks?

• Do we act according to the principle ”Right from me”?

• Do we have uncontrolled waste without eliminating it?

• Are we aware of improvement ideas?

• Continuous improvements. Learn from earlier projects

• ”Walk – don’t run”!

• Celebrate success!

24

testing and lean principles eurostar 2010 · testing approach • built on values and principles in...

Documents