The Tester's Role in Agile Planning

W3 !Concurrent)Session)4/10/2013)10:30)AM)

)))

"The Tester’s Role in Agile Planning" )))

Presented by:

Rob Sabourin

AmiBug.com )))))))))

Brought(to(you(by:()

))

340)Corporate)Way,)Suite)300,)Orange)Park,)FL)32073)888#268#8770!∙!904#278#0524!∙[email protected]!∙!www.sqe.com!

!

!!!!

!!!!!!Rob!Sabourin!!!!AmiBug.com!!

!!!!Rob Sabourin, P. Eng., has more than thirty years of management experience leading teams of software development professionals. A well-respected member of the software engineering community, Rob has managed, trained, mentored, and coached hundreds of top professionals in the field. He frequently speaks at conferences and writes on software engineering, SQA, testing, management, and internationalization. Rob wrote I am a Bug!, the popular software testing children's book; works as an adjunct professor of software engineering at McGill University; and serves as the principle consultant (and president/janitor) of AmiBug.Com, Inc. Contact Rob at [email protected].!

1

AmiBug.Com, Inc. March 27, 2013 © Robert Sabourin, 2012 Slide 1

The Tester’s Role in Agile Planning

Robert Sabourin

President AmiBug.Com, Inc. Montreal, Canada

[email protected]

AmiBug.Com, Inc. Slide 2


March 27, 2013 © Robert Sabourin, 2012

•  Robert Sabourin , Software Evangelist

•  President •  AmiBug.Com Inc. •  Montreal, Quebec,

Canada •  [email protected]

2

AmiBug.Com, Inc.


March 27, 2013 © Robert Sabourin, 2012 Slide 3

What is the problem?

Testing silo

Not really done

Shallow testing

AmiBug.Com, Inc.



Tester participation

Not invited

Not involved

Not engaged

3

AmiBug.Com, Inc.



What happens? Testers are bored

Programmers dominate discussion

“Quality discussions” don’t take place

AmiBug.Com, Inc.


•  “Testers attend Scrum meetings but are bored to tears”

•  “Testers do not engage in discussions”

•  “Planning is driven by programmers debating how to do things”


4

AmiBug.Com, Inc.



Testing ideas

Limited

Repetitive

Experience bound

AmiBug.Com, Inc.



Tester participation

Why check?

Why think?

Why bother?

5

AmiBug.Com, Inc.



Thoughtless planning

“Test the story”

Template activities

Document centric

AmiBug.Com, Inc.



Waterfall inertia

Test requirements

Test scripts

Test executions

6

AmiBug.Com, Inc.



Locked into silly approach

Tool centric workflow

Job relates to using a tool

Tool takes thinking out

AmiBug.Com, Inc.



Agile planning

Less paperwork

More thinking

Combine dev & test

7

AmiBug.Com, Inc.



Defining done

Organizational

Who decides

How do we know?

AmiBug.Com, Inc.



Undefined done

Business risks

Technical risks

Inconsistent testing

8

AmiBug.Com, Inc.



Weak examples of done

Developer says …

Stakeholder says …

Calander says …

AmiBug.Com, Inc.



Product backlog Customer originates

Product owner prioritizes

Single wringable neck

9

AmiBug.Com, Inc.



The tester and the backlog

Tester elicits story tests (checks)

Story tests are clear examples

Story tests are acceptance criteria (fit)

AmiBug.Com, Inc.



Story tests include

Normal flow

Alternate flow

Error flow

10

AmiBug.Com, Inc.



Story tests collected for

Functional requirements

Non functional requirements

Product deliverables (documentation, training etc)

AmiBug.Com, Inc.



Grooming sessions

Clarify story

Elicit story tests

Size stories

11

AmiBug.Com, Inc.


•  “Tester can also propose backlog entries”


AmiBug.Com, Inc.



Planning meeting style

Per Sprint

Per Story

Hybrid

12

AmiBug.Com, Inc.


•  “Sprint plan is dynamic”


AmiBug.Com, Inc.



Testing Tasks

Infrastructure

Data

Customer facing

Non functional

Robustness

Exploratory charters

Development facing

Business rules

Information

Learning

13

AmiBug.Com, Inc.



Infrastructure Tools

Frameworks

Test Automation

Test Environments

Test Data

Test Equipment

AmiBug.Com, Inc.



Data Generation

Capturing

Organization

Validation

Modeling

Scripting

Migration

Synchronization

14

AmiBug.Com, Inc.



Customer facing Story Testing

Cross-Functional Testing

Non story related functionality

Testing with customer data

Pairwise combination testing

Pareto combination testing

Elicit usage scenarios from customers

AmiBug.Com, Inc.



Non functional Accessibility

Auditability

Availability

Backup / Recovery

Capacity

Compatibility

Compliance testing

15

AmiBug.Com, Inc.



Non functional Deployment / Installation / Patching

Documentation, Help, Training

Dynamic analysis

Efficiency

Environment

Failure management

Internationalization, Localization

AmiBug.Com, Inc.



Non functional Interoperability

Load (many concurrent threads)

Operability

Performance

Review framework data

Scalability

Security

16

AmiBug.Com, Inc.



Non functional Static analysis

Stress

Usability

Volume (High)

AmiBug.Com, Inc.



Robustness Software Breaking

Failure simulation

Timeout across multiple tiers, handshaking failure

Buffering between tiers

Transaction arrival rates

Corrupt or lost data

Error recovery

Stress testing

Data fuzzing

17

AmiBug.Com, Inc.




Capability confirmation

Creative Ideas

Cross Story Relationships

End to End

Experience based charters

Gaps in story testing

AmiBug.Com, Inc.




Gaps in unit testing

Sequences of operations

State models

Usage Scenarios

White Box

Resource contention sharing

18

AmiBug.Com, Inc.



Regression Related

Automate regression testing

Design new regression tests

Exploratory regression testing (focus)

Run unit test regression suite

Run story test regression suite

AmiBug.Com, Inc.



Development facing

Features are controllable via API

States are observable via API

Add fixtures for story tests

Create test automation scripts

Design tests for TDD

Create executable story tests

Structural tests

Integration tests

Design review

Code review

19

AmiBug.Com, Inc.



Business rules Constraints

Decision tables

Workflow

Regulations

Conflicts

Business analysis

AmiBug.Com, Inc.



Information related

Sharing with other teams

Sharing with stakeholders

Sharing within the team

Mandated documents

Demos

20

AmiBug.Com, Inc.



Learning Development models

Business models

Technology

Tools & techniques

How system is used

AmiBug.Com, Inc.



agile team

21

AmiBug.Com, Inc.



flexible

AmiBug.Com, Inc.



graceful

22

AmiBug.Com, Inc.



philosophy

AmiBug.Com, Inc.



proudly proponder

23

AmiBug.Com, Inc.



recommending

AmiBug.Com, Inc.



passionate pleader

24

AmiBug.Com, Inc.



ardent advocate

AmiBug.Com, Inc.



sage advisor

25

AmiBug.Com, Inc.



team member

AmiBug.Com, Inc.



social responsibility

26

AmiBug.Com, Inc.



ethics

AmiBug.Com, Inc.



wise counsellor

The Tester's Role in Agile Planning

Technology

Transcript of The Tester's Role in Agile Planning