Solving the puzzles of agile testing
    Matthew Steer




                      Unissons nos Talents

TALENTED   TOGETHER...
About me…


              Agile Testing Practices Lead

              Certified Scrum Master

              12 years in th...
Definition of Done


 Provide a simple, yet effective way to visualise the testing
 function

 Highlight the impacts that ...
But first…


 Who is succeeding and is recognising benefits from agile?



 Who feels they are agile ‘ready’ and want to p...
We need
something
to grab their
attention…




                5
The puzzle analogy – Rubik’s cube


The cube is your                   Colours are scattered
testing function…            ...
The puzzle analogy – shared colours




                   People




     Process                    Tools




          ...
Common anti-patterns




                      Unissons nos Talents

TALENTED   TOGETHER

                                ...
Disclaimer…




              9
A major and common anti-pattern




Always playing catch-up…            10
Our projects…




            11
Agile engineering
       practices!?




                 12
Our agile test approach…




                           13
Testing on firm
 foundations…




              14
We do it like
this because
    the book
    says so…




            15
Where we keep our test
          automation




                     16
The truth hurts…




               17
The puzzle analogy – solving the puzzle


 Know your ‘starting point’

 Understand your ‘agile readiness’

 Complete remed...
Agile Testers !?   19
Our DTS…   20
Our DTS…   21
Summary


 Use simple methods for communicating

 Your ‘state of readiness’ will help identify your puzzles

 Puzzles may ...
Before you embark on the journey…


 Plan your transition

 Do not blame agile for immature or volatile processes

 Avoid ...
Final thought…




                 24
Definition of Done




          Done?

                     25
Definition of Done


 Provide a simple, yet effective way to visualise the testing
 function

 Highlight the impacts that ...
Thank-you
    msteer@uk.sopragroup.com

           @steer_matthew




                            Unissons nos Talents

TA...
Upcoming SlideShare
Loading in …5
×

Solving The Puzzles Of Agile Testing [V1.0 Final With Antipatterns]

809 views

Published on

Agile Testing Days presentation

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
809
On SlideShare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Solving The Puzzles Of Agile Testing [V1.0 Final With Antipatterns]

  1. 1. Solving the puzzles of agile testing Matthew Steer Unissons nos Talents TALENTED TOGETHER 1
  2. 2. About me… Agile Testing Practices Lead Certified Scrum Master 12 years in the Testing Industry Experienced in waterfall and agile methodologies @steer_matthew Matthew Steer Senior Test Consultant Acc Sopra Group UK Tel : +44 (0)121 5069180 Mob: +44 (0)7860 906332 http://uk.linkedin.com/in/steermatthew Email: msteer@sopragroup.com 2
  3. 3. Definition of Done Provide a simple, yet effective way to visualise the testing function Highlight the impacts that agile has on the testing function Discuss common anti-patterns Confirm why a ‘state of readiness’ is vital for any agile transition plan 3
  4. 4. But first… Who is succeeding and is recognising benefits from agile? Who feels they are agile ‘ready’ and want to pilot something? Who is unsure of whether they are agile ‘ready’? Who has tried and failed with agile? 4
  5. 5. We need something to grab their attention… 5
  6. 6. The puzzle analogy – Rubik’s cube The cube is your Colours are scattered testing function… differently… Your cubes share How do we solve the the same colours… puzzle? 6
  7. 7. The puzzle analogy – shared colours People Process Tools 7
  8. 8. Common anti-patterns Unissons nos Talents TALENTED TOGETHER 8
  9. 9. Disclaimer… 9
  10. 10. A major and common anti-pattern Always playing catch-up… 10
  11. 11. Our projects… 11
  12. 12. Agile engineering practices!? 12
  13. 13. Our agile test approach… 13
  14. 14. Testing on firm foundations… 14
  15. 15. We do it like this because the book says so… 15
  16. 16. Where we keep our test automation 16
  17. 17. The truth hurts… 17
  18. 18. The puzzle analogy – solving the puzzle Know your ‘starting point’ Understand your ‘agile readiness’ Complete remedial activities to remove impediments Plan for agile transition …but don’t just limit to testing! 18
  19. 19. Agile Testers !? 19
  20. 20. Our DTS… 20
  21. 21. Our DTS… 21
  22. 22. Summary Use simple methods for communicating Your ‘state of readiness’ will help identify your puzzles Puzzles may be shared, most will be unique to your organisation There are no silver bullets for this! 22
  23. 23. Before you embark on the journey… Plan your transition Do not blame agile for immature or volatile processes Avoid at all costs... Rapid Application Disaster Fragile ScrumBut Wagile Scrummerfall Rollout agile using agile 23
  24. 24. Final thought… 24
  25. 25. Definition of Done Done? 25
  26. 26. Definition of Done Provide a simple, yet effective way to visualise the testing function Highlight the impacts that agile has on the testing function Discuss common anti-patterns Confirm why a ‘state of readiness’ is vital for any agile transition plan 26
  27. 27. Thank-you msteer@uk.sopragroup.com @steer_matthew Unissons nos Talents TALENTED TOGETHER 27

×