THE TESTER ROLE & SCRUMHow do Testers fit into the Scrum Framework?

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

Scrum Framework [1]

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

Generalizing Specialists (or Specializing Generalists) [2]

KEY MESSAGE #1Competence defines what you do – not role

How to use Test Competence?• If you have competence within test, what can you use that

competence for?

• Testing? Obviously.

• Something else?

Agile Test Quadrants [3]

Code & Architecture Design• By supporting developers and software architects,

someone with test competence can help create better designed software

• Acceptance Criteria

• Testability

• Test Automation

Acceptance Criteria

Given / When / Then

Writing good Acceptance Criteria requires a testing skillset

Testability [5]

Test Automation

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

through test automation

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

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

Who tests what? (Simplification)

Anyone

Someone with System Competence

Someone with Test Competence

Someone with Test Competence

KEY MESSAGE #3Handling complexity is key component in test competence

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

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

KEY MESSAGE #4As someone with test competence you are an important part of the Scrum Team, that can support the team in unique ways

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

References

[1] The Scrum Guidehttp://www.scrumguides.org/docs/scrumguide/v1/scrum-guide-us.pdf[2]To combine … or nothttp://angryweasel.com/blog/to-combine-or-not/[3] Agile Testing Quadrantshttp://www.developsense.com/presentations/2014-06-Dublin-RSTAgileTesting.pdf[4] Acceptance Criteriahttp://www.leadingagile.com/2014/09/acceptance-criteria/[5] Heuristics of SoftwareTestabilityhttp://www.satisfice.com/tools/testable.pdf[6]Cynefinhttp://en.wikipedia.org/wiki/Cynefin