Tester’s fate in an agile


Published on

20 min sponsored talk presentation on Agile PT 2011 conference (http://2011.agilept.org/program/talk-tiago-pascoal).

Some slides are less than legible since they have animations. Apologies for that

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Tester’s fate in an agile

  1. 1. Tester’s fate in an Agile World: Extinction or Evolution? 21 June 2011<br />Tiago Pascoal<br />tiago.pascoal@agilior.pt<br />http://pascoal.net<br />
  2. 2. Disclaimer<br />Sponsored Talk<br />
  3. 3. Extinction or Evolution<br />
  4. 4. Before we Start<br />Scrum ⇎ Agile<br />Scrum ⇒Agile<br />Agile ⇏ Scrum<br />Agile should be a mean to an end, not an end to itself<br /> <br />
  5. 5. Robert Heinlein<br />A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.<br />in Lazarus Long<br />
  6. 6. What is Agile development?<br />Not even a mention on testing.<br />But this is Dilbert after all (or is it agile? )<br />
  7. 7. Why Agile?<br /><ul><li>Requirements are getting more complex, but also changing faster!
  8. 8. Product lifecycles are getting shorter
  9. 9. Proven results in multiple sectors
  10. 10. Unpredictable future</li></li></ul><li>It as all about the Flow<br />Why the previous slide?<br />Everyone takes this for granted...<br />
  11. 11. Scrum Teams<br />Team members often have specialized skills, such as programming, quality control, business analysis, architecture, user interface design, or data base design. However, the skills that Team member share – that is, the skill of addressing a requirement and turning it into a usable product – tend to be more important than the ones that they do not. People who refuse to code <br />because they are architects or designers are not good fits for Teams. <br />Everyone chips in, even if that requires learning new skills or remembering old ones. There are no titles on Teams, and there are no exceptions to this rule. Teams do not contain sub-Teams dedicated to particular domains like testing or business analysis, either.<br /> Ken Schwaber Scrum Guide (http://www.scrum.org/scrumguides/)<br />
  12. 12. So far....<br />This seems like a slam dunk<br />Perhaps Testers extinction is indeed their fate<br />(at least from organizations that do testing ... )<br />
  13. 13. But i’m here to argue otherwise<br />
  14. 14. Testers to dev ratios<br />Microsoft development division (devdiv) has a ratio of 1 between developers and testers (one tester per each dev)<br />One could argue they are not using agile, except most of the teams are: <br />Over 2/3 of the teams use some sort of Scrum<br />Entire division uses agile practices (unit testing, continuous integration,...)<br />Some (other) organizations have even higher ratios<br />Their clients do the testing <br />
  15. 15. Perhaps...<br />Make everything as simple as possible, but not simpler<br />
  16. 16. Agile Testing – 3 pillars<br />Agile mindset for People<br />Agile Practices in Process<br />Agile lifecycle Tools <br />
  17. 17. Agile Mindset for People<br />Collaboration<br />Trust & Transparency<br />Flexibility in roles and responsibilities<br />Responding to change <br />
  18. 18. Agile Testing Process<br />
  19. 19. Agile Practices for testers<br />Stand up meetings <br />User story reviews<br />Acceptance test driven development (ATDD)<br />Business driven testing (BDD)<br />Team design reviews<br />Pair testing <br />Exploratory testing<br />
  20. 20. AgileTools<br />Agile testing needs tools that support<br />Team collaboration<br />Reduction of waste<br />Transparency & visibility<br />A holistic approach to Application Lifecycle Management<br />
  21. 21. Exploratory Testing<br />Dogfood IDC NAR<br />
  22. 22. Exploratory Testing<br />Exploratory testing with tooling is almost inefective. It is optimal to have a tool that collects evidence of the tests effortlessly<br />Video Recordings<br />Screenshots<br />Action Recording<br />UI Actions<br />System Information<br />Application Traces<br />Dogfood IDC NAR<br />
  23. 23. Actionable bugs<br />Repro steps<br />Actions on bug <br />Video recording<br />Intellitrace ™ <br />Screenshots<br />Comments<br />Debug logs<br />Event logs <br />System information <br />Snapshot<br />
  24. 24. Shared test automation<br />Dogfood IDC NAR<br />
  25. 25. Continuous integration<br />Dogfood IDC NAR<br />
  26. 26. Automatic Test Impact Analysis<br />Dogfood IDC NAR<br />
  27. 27. Transparent project management<br />
  28. 28. Visual Studio 2010<br />
  29. 29. Objectives toward an agile testing<br />Agile Mindset for People<br /> Collaboration, transparency, flexibility <br /> Respond to change quickly<br />Agile Processes <br />Quality shared responsibility from day one<br />Pick practices that suit your team – exploratory testing, pair testing, CI etc.<br />Agile Tools <br />Pick tools that are friction free <br />Use tools that break siloes between dev and test <br />
  30. 30. My talk in a picture <br />
  31. 31. Quod Erat Demonstratum<br />I hope. <br />Questions?<br />
  32. 32. Resources<br />www.microsoft.com/visualstudio<br />www.microsoft.com/visualstudio/en-us/products/2010-editions/test-professional/overview<br />