© BJSS Limited 2012 Commercial in Confidence

Tester's Agile Pocketbook

Stevan.zivanovic@bjss.com

#stevanzivanovic

© BJSS Limited 2012 Commercial in Confidence

Section Heading

© BJSS Limited 2011 Commercial in Confidence 1 © BJSS Limited 2011 Commercial in Confidence 2 © BJSS Limited 2012 Commercial in Confidence

Section Heading

© BJSS Limited 2011 Commercial in Confidence 1 2

What is this talk about?

• My top 5 (off many ) tips from working

on Agile projects

in Enterprise environments

What is agile?

3

• It is not a set of process and procedures that

are “done to” people

People

Adaption

Learning

Delivery

Creating

Skills

4

“Adopt the Principles

Adapt the Practice”

Gojko Adjic

BATD '11

© BJSS Limited 2012 Commercial in Confidence

Section Heading

© BJSS Limited 2011 Commercial in Confidence 1 © BJSS Limited 2011 Commercial in Confidence 2 © BJSS Limited 2012 Commercial in Confidence

Section Heading

© BJSS Limited 2011 Commercial in Confidence 1 2

Why Enterprise Agile?

• Agile and big business presents challenges

• The attitudes, adaptability and flexibility

that Agile teams can bring are a benefit

• However some aspects of corporate

governance, auditing, financial constrains

add to the opportunities

Managing the process

6

• Plan

Plan on what you know

Clearly show what is assumed

• Iterate

Learn, review, adapt the plan

• Communicate

Ensure everyone is aware of what you are

doing!

Innovate on how you communicate – wider

stakeholders

Test Techniques

7

• Utilise your test techniques (RBT, Use

Cases, BVA, Decision Tables, etc)

• User Stories • As a tester

I want to have requirements that actually mean

something and are testable

So that I can provide relevant and useful feedback

• Test driven approaches to structuring your

project provide benefits

Models

8

• Build a model of your system under test

• Use it to report against

ETL for

EC 2

ETL for

EC 1

Message

Queue

Message Creation

Middle Office

Systems

Processing

ApplicationReference

Data 2

KEY

Reference

Data 1

Internal Deal

Input

Coverter

External Deal

input

External

Company 1

Message 1

Release vehicle

Released

In test

Firewall

In Dev

Planned

Message 2

Response

Errors

Not tested

Partially Tested

Fully Tested

Workflow test status

External System

External

Company 2Out of Scope

Spec expected 14 Sept

Dev start expected 1st Oct

A warning on metrics

9

• In a car a dashboard allows you to answer

important questions regarding your current

status such as ...“Speed”?

• Answering these questions alone though

does not guarantee a trouble free journey. (BJSS Enterprise Agile Book)

Sorry officer,

I was watching

my speed....

Who Tests – Who Checks?

10

• Checking and Testing (Michael Bolton -

http://www.developsense.com/blog/2009/08/testing-vs-

checking/)

“Checks Are Machine-

Decidable; Tests Require

Sapience”

Automation

11

• Plan to use automation from the start of the

project - “Prepare to be automation ready” - Jonathan Wright

• Let it grow organically, but as any good

plant you need good roots

• Regular (multi - daily?) test runs – run the

valuable tests that you need that day

• Use automation to assist definition your

tests (First Day automation – Experiences in Test Automation)

In Summary

12

© BJSS Limited 2012 Commercial in Confidence

Section Heading

© BJSS Limited 2011 Commercial in Confidence 1 © BJSS Limited 2011 Commercial in Confidence 13 © BJSS Limited 2012 Commercial in Confidence

Section Heading

© BJSS Limited 2011 Commercial in Confidence 1 13

Thank you

• Resources:

• Enterprise Agile book:

•http://bjss.com/enterprise-agile/index.php

•Testing Booklet – in Beta version

• Available on request – see me

14

Brian?

The only person you

can reliably influence

and change is you!