Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

The Tester Role & Scrum

15 167 vues

Publié le

My views on a tester's place in the Scrum Framework.

Publié dans : Ingénierie, Technologie
  • Unlock Her Legs is your passage way to a life full of loving and sex... read more >>★★★ https://tinyurl.com/y52uv4vq
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Nice !! Download 100 % Free Ebooks, PPts, Study Notes, Novels, etc @ https://www.ThesisScientist.com
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Thanks, For Free Download Latest PPTs You will also Visit Us www.ThesisScientist.com
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Great stuff Johan, you got a solid 4,5 out of 5 for this presentation at the testit2015 conference. Thank you!
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici

The Tester Role & Scrum

  1. 1. THE TESTER ROLE & SCRUM How do Testers fit into the Scrum Framework?
  2. 2. Introduction – This presentation • This presentation outlines my views on a tester’s place in the Scrum Framework • This is based on my experiences in my context, and may or may not be applicable to you
  3. 3. Scrum Framework [1]
  4. 4. The Tester Role How do we define the Tester role? Do we need to define the Tester role? Competence, not role, is the key in this discussion
  5. 5. Generalizing Specialists (or Specializing Generalists) [2]
  6. 6. KEY MESSAGE #1 Competence defines what you do – not role
  7. 7. How to use Test Competence? • If you have competence within test, what can you use that competence for? • Testing? Obviously. • Something else?
  8. 8. Agile Test Quadrants [3]
  9. 9. Code & Architecture Design • By supporting developers and software architects, someone with test competence can help create better designed software • Acceptance Criteria • Testability • Test Automation
  10. 10. Acceptance Criteria Given / When / Then Writing good Acceptance Criteria requires a testing skillset
  11. 11. Testability [5] The practical testability of a product is how easy it is to test* by a particular tester and test process, in a given con- text†. Practical testability is a function of five other  “testabilities:”  project-related testability, value-related testability, subjective testability, intrinsic testability, and epistemic testability  (also  known  as  the  “risk  gap”). Just as in the case for quality in general, testability is a plastic and multi-dimensional concept that cannot be usefully expressed in any single metric. But we can identify testability problems and heuristics for improving testability in general. Interesting Testability Dynamics
  12. 12. Test Automation With competence both in test and in automation a person can add value through test automation
  13. 13. Coaching & Retrospectives • Someone with test competence should also coach the other members of the Scrum Team to improve their competence in this area • During the Sprint Retrospectives someone with test competence could also provide a different perspective on what went well and what needs to be improved for future sprints
  14. 14. KEY MESSAGE #2 Testing is infused into everything & test competence can be valuable in many activities
  15. 15. Who tests what? (Simplification) Anyone Someone with System Competence Someone with Test Competence Someone with Test Competence
  16. 16. KEY MESSAGE #3 Handling complexity is key component in test competence
  17. 17. Competence not Role • Everyone is a tester, but not everyone has the competence to handle those complex testing problems • Focus on your competence and continuously develop it – don’t put any value in what your role is called
  18. 18. Test Competence in a Scrum Team • The Development Team is responsible for testing • Each developer is responsible for testing whatever he/she develops • But sometime they may need some help • If the team dumps all their testing on you, the team is not working properly and this should be brought to the Scrum Master’s attention • But with Test Competence you are in a unique situation to help other members of the team to investigate complexity • Help the team with complex test problems • Allow and support the team to handle simple and complicated test problems themselves
  19. 19. KEY MESSAGE #4 As someone with test competence you are an important part of the Scrum Team, that can support the team in unique ways
  20. 20. Conclusion • Competence defines what you do – not role • Testing is infused into everything & test competence can be valuable in many activities • Handling complexity is key component in test competence • As someone with test competence you are an important part of the Scrum Team, that can support the team in unique ways
  21. 21. References [1] The Scrum Guide http://www.scrumguides.org/docs/scrumguide/v1/scrum-guide-us.pdf [2]To combine … or not http://angryweasel.com/blog/to-combine-or-not/ [3] Agile Testing Quadrants http://www.developsense.com/presentations/2014-06-Dublin-RSTAgileTesting.pdf [4] Acceptance Criteria http://www.leadingagile.com/2014/09/acceptance-criteria/ [5] Heuristics of SoftwareTestability http://www.satisfice.com/tools/testable.pdf [6]Cynefin http://en.wikipedia.org/wiki/Cynefin

×