revolution, evolution and 'lean: a test process improvement diary from copenhagen to...
DESCRIPTION
The move from a waterfall life cycle to an agile one is not straightforward for people with a long experience in software development and testing. The ways of working are in their backbones and hard to change. In this kind of situation, taking small steps towards the right direction simply takes too long. You need to throw away your old process (=Revolution) and then improve the new process constantly (=Evolution). Usually, it is not possible to have a full scale revolution at once. That makes the evolution even more important, to get rid of the bad practices from the time before the revolution. An effective approach to speed up the evolution is to take the seven wastes of lean management as a guideline – to detect and remove relics not blown away by the revolution. This presentation is my diary for test process improvement, spanning from Eurostar 2010 in Copenhagen and the Workshop on Lean Test Management (by Bob van de Burgt & Iris Pinkster), to the 2011 conference in Manchester. It highlights in interesting and surprising ways the evolution of three agile teams in a major Finnish company. Waste is often produced by applying good practices in the wrong place, e.g.because of a weak test strategy or by involving too many people in defect management. Waste can also be caused by very practical things like bad seating arrangements or people not attending meetings. However, the biggest waste is to optimize the wrong things – e.g. the detection of defects instead of their prevention. These are examples of the things that have come up so far – but there will more during the year. I will also introduce some practical and light ways to measure the consequences of the waste.TRANSCRIPT
Revolution, Evolution and Lean - a Test Process Improvement Diary from Copenhagen to Manchester.Tapani AaltioSogeti FinlandNov 24, 2011
Revolutiona drastic and far-reaching change in ways of thinking and behaving
Eugène Delacroix - La liberté guidant le peuple, 1833. ( Liberty Leading the People)
Source: wordnetweb.princeton.edu
Agile Test Process?
Plan Prep Spec Exec Comp
Infra
Ctrl
developmenttests
acceptancetests
systemtests
functional
Design
realisation
operation & management
wish, legislation, policy,
technical
design
opportunity , problem
requirements
input for
input for
input for
input for
input for
input for
Scrum Cycles
TMap Test Process
V-Model
The Project The system
Identity management: register, sign-in, sign-out, profile management, sso Used by around 50 services with 150 million users No downtime, response times under 1 sec
People Pool of 25 people, three scrum teams Developer:tester -ratio 1:1
Testing ”Manual testing is our worst enemy” 3000 automated unit and integration tests 1000 automated black box tests Test automation framework based on Ruby/Watir, built by the team Manual integration testing and acceptance testing with customers
Scrum Sprint cycle two weeks, release cycle 4-6 weeks
The Seven Wastes of Lean Management
OverproductionWaiting
Unnecessary inventoryTransporting
Inappropriate processingExcess motion
Defects
How to Estimate Effort Without Creating Waste?
Planning poker Estimate complexity of
backlog items Fast way to create a
common understanding among the team
Used to measure the velocity of the team
Testers participate on day one
Overproduction Inappropriateprocessing
How to Organize Work Without Creating Waste?
Sprint planning commitmentDefinition of done
Short commitments, several releases
Overproduction Waiting Inventory
Applying Good Practices “Just in Case” Is Waste
Prioritizing test cases
Linking requirements to test cases
Linking test cases to defects
Overproduction Inappropriateprocessing
Manual Testing and Manual Reporting Are Waste
Manual testing is our worst enemy
Test levels are concurrent, not back-to-back
Instant, continuous feedback and reporting
Creating test reports manually is waste
InventoryOverproduction
TesterDevelope
r
Defect Management is Waste!
Nieuw
BO
Afgewezen
Onderzoek
Toegewezen Uitgesteld
Oplosser
In hertest
TM
Hertest ok
TesterHertest niet ok
Niet opgelost
Tester
= Status
= Person/ meeting who adjusts the status
TM = Test manager
Andereoplossing
New
DC
Rejected
Analysis
Assigned Postponed
Solved
Solver
In re test
TM
Re test ok
TesterRe test not ok
Notsolved
Tester
= Status
Othersolution
Throw it in the cloud!
Overproduction Waiting Inventory Transporting
Excess motion
Inappropriateprocessing
Defects
Instead of this…
Create a test case to demonstrate a failure, work
together!
EvolutionA process in which something passes by degrees to a different stage (especially a more advanced or mature stage) Source: wordnetweb.princeton.edu
Evolution of scrum teamsEvolution of species
How to Apply Revolution and Evolution?
Have the courage to change, don’t be blown away by the revolution.
Don’t be afraid of bad ideas - you might block fantastic ideas!
OverproductionWaiting
Unnecessary inventoryTransporting
Inappropriate processingExcess motion
Defects