1. Seeking ‘a’gile Testing
Robert Manger – Senior Test Analyst

2. Seek Context – Numbers & Facts
>14 years old
Sales, Advertising & Marketing Company
5 technology platforms
~7 project streams (in IT alone)
After several false starts didn’t want to be ‘Agile’
Focused on problem of Speed to Market
‘a’gile was the answer

3. XP (Extreme Programming)
Agile flavours at Seek
XP (Extreme Programming)
Kanban
Lean
Scrum

4. Agile flavours at Seek “It’s not about adopting ‘Agile’.
XP (Extreme Programming)
Teams use a combination of whatever makes sense to them
Kanban
Lean
Scrum
“It’s not about adopting ‘Agile’.
It’s about using agile techniques to get better”

5. People Tools Process High Level Scope Roles and Responsibilities
Attitudes and Perceptions
Tools
Some of the tools we use to help us in our jobs
Process
How we ensure we are maintaining and measuring a high level of quality while ensuring speed

6. People

7. Distinct Roles within a Successful Team
Agile Myth: We Don’t Need Testers
Source: Craig Smith - Suncorp
Quality and Testing is a joint effort for all parties involved

8. Changing Roles & Responsibilities
Business Analyst
Tester
Developer
Code
Customer
Exploratory Testing
Security
Performance
Automation
Manual Scripted
Requirements
Unit Testing
Testing is more important than ever, but it is evolving

9. Tools

10. Agile Myth: We Don’t Need Tools
Choosing a Toolset
Agile Myth: We Don’t Need Tools
There’s no such thing as a Silver Bullet

11. The Right Tools for the Job
Choosing a Toolset
Too much?
Too little?
The Right Tools for the Job

12. Use what you need to get the job done
SnagIt
CTE XL
NetLimiter
Selenium
Custom Test
Harnesses
Nunit
Resharper
SpecFlow
MS TFS
Test Manager
SAP GUI
StresStimulus
The tools do not dictate how you do your job
They help you to do a better job

13. Process

14. Agile Myth: We Don’t Need Planning or Documentation
A Working Process
Agile Myth: We Don’t Need Planning or Documentation

15. “Quality Gateways” through the whole process
0 - Inception
1 - Story Workshop
2 - Story Kick-off
3 – Parallel Development and Test Planning
4 - Story Walkthrough
5 - Test Execution
6 - Showcase
7 - Retro

16. Everyone is involved at every step along the way
Quality Gateways
0 – Inception
1 – Story Workshop
2 – Story Kick-off
3 - Test Planning
4 – Story Walkthrough
5 – Test Execution
6 – Showcase
7 – Retro
Everyone is involved in Project definition
Everyone has input into the requirements and estimates
Developers are absolutely clear on what they need to do
Parallel Development and Test Planning
Testers are absolutely clear on what they are getting
Stakeholders get a chance to give feedback
Everyone has a chance to improve!
Everyone is involved at every step along the way

17. End to End traceability is automatically maintained
4 – Test Execution
~60% of Test Effort lies in Automation
~40% of Test Effort lies in Manual/Exploratory
Reports
API
Selenium
Custom
End to End traceability is automatically maintained

18. Reporting is automatically generated
Reporting should be customised depending on the intended audience

19. Summary Testers are increasing their skillsets
Testing is known to be an integral part of a strongly cohesive team
There is no one “right” way of doing things
Testers (and BAs) are now driving the development
There is no hidden effort across the whole project
We can easily respond to change
Testers determine their own toolsets
A continuously improving process
This is just the tip of the iceberg
The journey has only just begun….

20. Questions & Contact
Robert Manger
@robertmanger