agile testing is nonsense, because agile is about testing!

Agile Testing is nonsensebecause Agile it’s all about testing…

Andrea Tomasini

Agile Coach & Trainer andrea.tomasini@agile42.com

@tumma72@agile42/coaches

Agile Testing is nonsense, because Agile is Testing

Testing is an attitude which brings us to trust results based on the fact that we can validate them. Testing is an approach which allows us to think about how to verify we did the right thing even before starting. Testing is a practice which allows us to write effective tests that can be repeated indefinitely while systematically producing consistent results. !

Agile Testing is nonsense, because Agile is Testing

Agile is built around the idea of managing complex projects, recognizing the importance of emerging results and verifying in a very disciplined way the assumptions and hypothesis we make as often and as thoroughly as possible. This means testing everything we do, every day … So if you are truly Agile, you are living testing in every second of your life!

Testing as an Attitude...

attitude: a settled way of thinking or feeling about something: he was questioned on his attitude to South Africa | being competitive is an attitude of mind .

Agile Values & PrinciplesAgile Values & Principles are supporting teams developing the right attitude to enable continuos and regular value delivering to the client, while continuously improving

Individuals & interactions

Working software

Customer collaboration

Responding to change

Processes & tools

Comprehensive documentation

Contract negotiation

Following a plan

o v e r

We recognize the value here...We value

this more….

Empirical Process ControlSwitching from measuring compliance to measuring outcome

Defined Process ControlThe time required to complete a repeatable action is a valid proxy to predict time to finish the whole

10s 20s5s 15s

38 5280? 76? 69?

Empirical Process ControlEvery step performed while creating a new product is unique, only outcome can be trusted

Iterative and incrementalStop assuming you already know what the client wants and discover it while building it together

I need to move from A to B faster than by walking…

I am not that good at staying in equilibrium, I need something more stable…

I am stable now, but not fast as I would like to be, can we go faster?

I figure I am pretty tired in the evening, and though I like sport, I still need to be faster

Inspect the outcome and learn to validate your assumptions & hypothesis

What is this?

BUT… not Because clients do not trust that their money has been used wisely...

Unit Tests

Integration Tests

User Acceptance Tests

Ad-Hoc Tests

What you get as a result… ice-cream!

Testing as an Approach...

approach: a way of dealing with a situation or problem: we need a whole new approach to the job.

Experimenting new things, innovating, requires dedication and commitment…

We like to learn using short feedback loops

Sometimes we don't...

Why are we thinking about what to test and how to test it beforehand?

Reduce... Social Risk

Reduce... Schedule & Cost Risks

Reduce... Business Risks

Reduce... Technical Risk

With every step we want to learn something...

Testing as a Practice...

practice: the actual application or use of an idea, belief, or method, as opposed to theories relating to it: the principles and practice of teaching | the recommendations proved too expensive to put into practice.

Creating a Vision with StakeholdersPeter Senge, Vision Strategies

Effort

Co-Creating

Consulting

Testing

SellingTelling

Agile Teams normally work with User Stories to agree what needs to be built and how…As a Returning Customer, I

want to jump with one click to the checkout page, so that I can purchase good quicker

- Detail about payment are visible - Shipping address is visible - I can change quantity of the items

User Stories do have Acceptance Criteria on their back, Team wouldn't commit to them, without knowing when they would be considered finished

Backlog

Definition of Ready

Definition of Done

Shippable Product

Continuous ImprovementAgile Team achieve continuous improvement by deciding how to Test a new behavior or practice, even before starting introducing a change…

do not overload yourPeople

(無理

Unnecessary Variations (斑: mura) keep the Flow

remove non value addingActivities

Wasteful Activities

(無駄: muda)

Agile Teams also test their behavior constantly...

... and learn how to get better over time...

... BUT it's not about finding who's right and who's wrong!

Working Agreements 1. We want to pair when stories

are bigger than 2 points, so that we reduce risk

2. We want to work with ATDD on all stories, so that we will have a cleaner design

3. ...

Capturing behavior and motivation helps teams to measure their effectiveness

Toyota Kata & Lean A3 are very powerful together…

Accelerators Breaks

Goals & TryKeep

TDD on hard

Delay with designers

Active Learning Cycle provides guidance on what to change and what to expect from the changes…

Next: TDD on one story

Working Agreements 1. We want to pair when stories

are bigger than 2 points, so that we reduce risk

2. We want to work with ATDD on all stories, so that we will have a cleaner design

3. ...

Definition of Done ✓ Integrated in the staging

system ✓ all acceptance criteria are

fulfilled ✓ no regression ✓ PO has seen the story ✓ Performance ok

Definition of Ready ✓ User Story format ✓ Max 5pt. ✓ INVEST ✓ At least 2 Acceptance Criteria

All Stories worked

with TDD No extra effort

for infrastructure

Doing TDD on everything

1 size > estimated

90% coverage of

the code

organi

managed

PullIndividual

pliance

borati

onCompetition

s on v

Cultivation Competence

Control

personal

Actuality

Possibility

Collaboration

William Schneider - The four Core Cultures

Agile Values & Principles

Experiences

Beliefs

Actions

Results

CultureMan

The “Results Pyramid” is copyright of Partners in Leadership LLC

balanc

coaching is an ongoing long term investment

agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.agile42 | We advise, train and coach companies building software www.agile42.com | All rights reserved. Copyright © 2007 - 2009.

How do we know if this is working for us?

Goal PSF NC

Agile Strategy Map ™

Represent the Goal we want to achieve

Possible Success Factor (PSF) represent a hypothesis about a “factor” that would allow to achieve the Goal

Necessary Condition (NC), is what is needed in order to fulfill the Success Factor

How can we make sure we are not missing something?

PSF#1: we believe that by consolidating all projects in one Portfolio, we will be able to make better business decisions

NC#1.1

NC#1.2

NC#1.1.1

To verify the hypothesis we define what is needed in order to start a pilot aiming at verifying the validity of the PSF#1NC#1.1: we need to list at least 3 projects per product area

NC#1.1.1: we need to chose projects and define comparable dimensions such as: business value, impact, (cost?)NC#1.2: we need to define a sample Portfolio funnel, and check that Teams can deliver with the provided information

Ok, it worked… now what’s next?

Goal CSF#1 NC#1.1

NC#1.2

CSF#1: we have to consolidate all projects in one Portfolio, so that will be able to make better business decisions

NC#1.1.1

The Pilot was successful...

The Success Factor, becomes Critical (CSF)

1. Testing is an attitude, because if we embrace the Agile Manifesto and its principles, we have to accelerate learning, and this requires individual commitment to validate assumptions

2. Testing is an approach, it requires to systematically initiate everything we do by understanding the constraints, the expected outcomes, and the possible learnings

3. Testing is a practice, because once we develop the attitude and learned the approach, we will be able to emerge practices, which will make us more effective at learning

4. Everybody makes mistake, every mistake is an opportunity to learn, and we need to be ready to learn and capitalize on that experience. If we are not, it will be just a failure!

5. Testing is a Team responsibility. Stay away from boxing responsibilities into roles… you will hinder self-organization and shared commitment

More food for thought...

http://slideshare.net/tumma72

Copyrights noticeAll material produced in this presentation is protected by the Creative Common License 3.0 (by-nc-sa).

agile testing is nonsense, because agile is about testing!

agile teams

rights reserved

acceptance

cleaner design

business decisionsnc1

reduce risk

agile testing

agile

Technology

agile testing and testing in agile software development ·...

agile test planning with the agile testing

no nonsense agile retrospectives · no nonsense agile...

agile testing – embedding testing into agile software...

agile testing - presentation for agile user group

evolving agile testing - eurostar conference...evolving...

unit 1. agile testing - educatererindia.com · unit 1....

an overview of agile testing - agile testing with

agile testing days

agile mëtteg #5: agile testing

agile testing and testing in agile software development

agile testing and testing in agile software development ·...

agile testing for agile sparks kanban clients

testing in agile at agile thailand 2015

workshop agile testing - ctqb...workshop agile testing...

dmitry lebedev: agile testing using agile tools

cover your testing bases using the agile testing...

advanced topics in agile testing - the future - agile...

agile testing agile ottawa april 2015

agile testing