Agile Zet de Testwereld Op Zijn Kop 001

8/8/2019 Agile Zet de Testwereld Op Zijn Kop 001

http://slidepdf.com/reader/full/agile-zet-de-testwereld-op-zijn-kop-001 1/9

Atos, Atos and fish symbol, Atos Origin and fish symbol, Atos Consulting, and the fish itself are registered trademarks of Atos Origin SA. August 2006 © 2006 Atos Origin. Confidential information owned by Atos Origin, to be used by the recipient only. This document or any part of it, may not be reproduced, copied,

circulated and/or distributed nor quoted without prior written approval from Atos Origin.

Will Agile turn the test world on its head?Will Agile turn the test world on its head?

Peter Kalmijn



2 Custom presentation- or document control name

Agile Software Development

We are uncovering better ways of developing

software by doing it and helping others do it.

Through this work we have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on

the right, we value the items on the left more.

www.agilemanifesto.org




Why to go Agile anyway?

» Shorter time-to-market

» Better product quality

» Reduced waste of resources and material

» Better predictability of the end product

» Heightened team morale

DO not use Agile

» Safety critical systems

» Without interaction with the customer

» With monolithic large teams

» Without management support




How do I recognize real ‘Agile’?

» Iterations are used to develop the product

» Each Iteration delivers a working product

» Phases (Design-Build-Test) in each iteration are nearly

concurrent

» The team uses specific practices to keep the growingproduct fresh and flexible

» Teams are self-managing

» Lean principles and techniques eliminate waste whereverpossible

» Team members are highly skilled and disciplined




What Agile testers do

» Facilitate communication between the technical & businessstakeholders

» Support early validation of requirements

» Help the business stakeholders define acceptance criteria

» Create automated acceptance tests

» Expand scope of ‘acceptance’ tests

» Advise the team about overall risks, trends and progress

» Perform manual/exploratory tests on early-stage product

» Help to determine if your stories are well defined

» Suggest adding stories related to testability

» Do exploratory testing on early builds

» Verify the completion of stories as they are completed

The agile testing role might evolveand change into somethingcompletely different from what weknow of as testing today




WHAT does Agile change for testers?

An Agile tester..

» will communicate more, with your coders and yourcustomers.

» will need to have a deeper understanding of thetechnology and the code (or will rapidly gain)

» practices pair testing, i.e. collaborates with thedevelopers to get good tests you will share morerisk, and feel an increased sense of ownership

» is part of the team and attend all team sessions

» is an integral part of the planning game

» will no longer be the gatekeeper

‘The nature of the tester's role changes in iterative projects. We are no longer the high-profile victims, we are no longer the lonely advocates of quality, we are merely (!)competent service providers, collaborating with a group that wants to achieve high

quality.’Cem Kaner

the role of testers on Agile teams is still emerging




Agile test projects differ .. .. Agile people too

Delivery on the end of theproject

Big upfront design

upfront involvement

Fixed roles

Defined work processesand controls

Following the Plan

Plan driven, taskmaster

process guarantee,repeatable

Conservative, plan-oriented

Short increments andfrequent delivery in UAT

and BAT to real users

Delivery

Evolving according toStakeholder Value

Design

Active Stakeholder

participation

Stakeholders

Organic teamsTeams

Simple rules & openinformation

Processes

Responding to changePlan

guiding vision,communicating

(Test)Project

leader

result guaranteeOutcome

Agile




Evolving Agile test strategies

Trend

» Towards hybrid / blended approaches

» Appropriate testing strategies motivated by risk

Practice

» Feature wise pre-acceptance the Agile way

» Final acceptance (Business Acceptance Test) at the end

Combinations of agile elements with traditional approaches

» Long and mid-term estimation/planning: traditional plan driven

» Agile highly iterative/incremental approach

You can use all agile some of the time and some agile all of the time.




Discussion

T e s t i n g

w i l l n e v e

r b e t h e s a m e

T e s t i n g

w i l l n e v e

r b e t h e s

a m e

a g a i n . .

a g a i n . .

Individuals and interactions over processes and tools

Working software over comprehensive documentationCustomer collaboration over contract negotiation

Responding to change over following a plan

Documents

Agile Zet de Testwereld Op Zijn Kop 001