Abe 2012


Published on

Testers in the Agile World

Published in: Technology
1 Comment
  • Be the first to like this

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

No notes for slide

Abe 2012

  1. 1. Testers in the Agile world Wiktor Żołnowski @streser blog.testowka.pl www.agileszkolenia.pl
  2. 2. I considered myself a Tester (on my team)
  3. 3. “Tester is the most important role in the team”Tester is the most important role in the team because:- only testers and testing can add quality to the software...- thanks to them there are fewer bugs in the software...- they are adding high value to our products...- it is impossible to work in a team without testers...
  4. 4. “Only testers can add quality to software...?” Quality is not a result of software testing - testing is only quality control (and even not always this)...
  5. 5. “If you have testers in the team then thenumber of bugs in the software is lower...?” Amount of implemented bugs could be lower than without testers, but not always... Its not a tester who is responsible for implementing bugs or fixing them.. Testing is proving that there are bugs in the software not fixing them...
  6. 6. “Software testing adds value to the product” Software testing doesnt add any value to the product by itself... Try to do only software testing without programming...
  7. 7. “It is impossible to deliver high quality software without testers” There are many teams that work just fine without testers...
  8. 8. “Who is a tester?” “What is a tester?”Tester is a state of mind...Software testing is continuously stressing the productand hunting for bugs...Testing is not just clicking around...
  9. 9. “What is the role of a tester in an AgileTeam?” By "...Agile Team..." I mean collocated, cross-functional team... I dont believe in “Agile Testing Teams” etc...
  10. 10. “From the beginning...”Testing is not just creating and executing test scenarios...Its not even about test automation... Testing is the art of asking correct questions at the right time: What are you working on? How do you plan to implement it? What about our DoD? Can you name all the test cases which you will use in your unit tests? Is this feature ready for tests?
  11. 11. “What next?” Its no more: “We – Them” Now WE are the team, and WE have a common goal so WE will be working together...
  12. 12. “Feedback” Is our product working properly? Are there any major bugs still there that need to be fixed? What is the probability/risk of there being critical bugs that we didnt find yet? Is it Done? Is it Done WELL? Could we do this better than it is right now? Should we do this better?
  13. 13. “The team” Higher expectations... Agile means continuous improvement – also your personal improvement... Increasing our effectiveness – it means that we will need to automate some parts of our work..
  14. 14. “The Tester” You need to be prepared for any changes... You need to be pro-active... Asking questions is crucial...You need to find a way to react before bugs will be implemented... Its because: “Responding to changes over following a plan”
  15. 15. “Testers are (?) different than programers” Different point of view... Tester is closer to the customer... They behave as a user more than programers... Working with testers can be effective, because: “Individuals and interactions over process and tools”
  16. 16. “Tester is the most a very important role inthe team” Working with testers in the team could be very effective... Testers need to ask questions and be pro-active... Communication skills are crucial...
  17. 17. “There is no place for testers in the AgileWorld...”Why the hell testers arent mentioned in methodologies likeScrum or XP?
  18. 18. “Scrum tester?”In Scrum we have cross-functional teams where everyone iscalled “developer”...Could “developer” mean “tester”?There is Definition of Done – but there is more than one wayto assure that this done is done...
  19. 19. “XP tester?”In eXtreme Programming the most important part of testing istest automation...But can high quality be assured only by TDD, BDD or ATDD?Is there any place for non-technical testers?Even if they dont know how to automate tests they alwayscould learn how to do it...Could you even try Pair Programming with testers?
  20. 20. “Tester”Testers with their domain knowledge and experience could bevery helpful in the programming process...Their input into TDD or BDD can be crucial...They are closer to the customer... And we know that: “Customer collaboration over contract negotiation” is not always so easy...
  21. 21. “What next?”Tester is the most a very important role in the Agile Team!There is no a place for testers in the Agile Team!
  22. 22. “We are all testers?”Everyone is testing what she is doing – one way or another...Everyone likes to prove that something is broken...Everyone could ask questions mentioned before...
  23. 23. “We are the team”It is crucial to work together, as a team...Cross-functionality works only with cooperation...You can be the most senior programmer and the most juniortester in the team or you can be the most senior tester and themost junior programmer...We are the team and we have common goal which is: “Working software over comprehensive documentation”
  24. 24. FinallyThere are testers among us!Their knowledge is priceless...Testers could be valuable team members but you need tocreate proper environment for them...Empower them!
  25. 25. In the end... "There are no testers (mentioned) in the Agile world" ... But ... "Testers are very important members of agile teams." ... And ... "We are all testers."
  26. 26. So how many of you would call yourself atester now? Wiktor Żołnowski wiktor.zolnowski@gmail.com www.agileszkolenia.pl www.byop.pl www.blog.testowka.pl