'

The Tester Role & Scrum

Понравилась презентация – покажи это...





Слайд 0

The Tester Role & Scrum How do Testers fit into the Scrum Framework?


Слайд 1

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


Слайд 2

Scrum Framework [1]


Слайд 3

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


Слайд 4

Generalizing Specialists (or Specializing Generalists) [2]


Слайд 5

Key Message #1 Competence defines what you do – not role


Слайд 6

How to use Test Competence? If you have competence within test, what can you use that competence for? Testing? Obviously. Something else?


Слайд 7

Agile Test Quadrants [3]


Слайд 8

Code & Architecture Design By supporting developers and software architects, someone with test competence can help create better designed software Acceptance Criteria Testability Test Automation


Слайд 9

Acceptance Criteria Given / When / Then Writing good Acceptance Criteria requires a testing skillset


Слайд 10

Testability [5]


Слайд 11

Test Automation With competence both in test and in automation a person can add value through test automation


Слайд 12

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


Слайд 13

Key Message #2 Testing is infused into everything & test competence can be valuable in many activities


Слайд 14

Who tests what? (Simplification) Anyone Someone with System Competence Someone with Test Competence Someone with Test Competence


Слайд 15

Key Message #3 Handling complexity is key component in test competence


Слайд 16

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


Слайд 17

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


Слайд 18

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


Слайд 19

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


Слайд 20

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


×

HTML:





Ссылка: