How testers can be a liability
@ulrikama
Ulrika Malmgren
Testers break stuff
@ulrikama
Programmers can't test their own code
@ulrikama
@ulrikama
Factors which affect quality
@ulrikama
Quality of the conversations
@ulrikama
Quality of the conversations
@ulrikama
Temperature reading - Virginia Satir
Measuring collective intelligence - MIT
Ways of working
@ulrikama
User Story Map - Jeff Patton
@ulrikama
@ulrikama
User Story Mapping
@ulrikama
User Story Mapping
@ulrikama
User Story Mapping
Scenarios
@ulrikama
Given ...
When ...
Then ...
Mind Maps
@ulrikama
Techniques to identify problems
@ulrikama
@ulrikama
Reading tip! Elisabeth Hendrickson - Explore it!
Testing dojos
@ulrikama
San Francisco DePOT
@ulrikama
San Francisco DePOT
@ulrikama
Bug hunt with retrospective
@ulrikama
Experience report - Ulrika Malmgren
Testing quadrants and how they relate to our team
Definition of done
Definition of ready
Checked vs explored
Who are our stakeholders?
How can we test earlier?
Zero bug policy - book circle
Root cause analysis
Bug analysis
@ulrikama
Don't be a risk!
@ulrikama
Raise the knowledge level of your team
Reflect on communication
Work with understanding
Sharpen your tools
Testers - Don't be a liability
By Ulrika Malmgren
Testers - Don't be a liability
Presentation @ Booster conference in Bergen 2016 Abstract "- You know, testers in a team can be a liability for the quality of your product. - How can you even say that? We hire testers to improve quality! Besides, aren't you a tester? - Yes, and because I know of this risk I can do a better job. - Alright, I'm intrigued... how? - Look, there are three main perspectives to keep in mind when talking about quality and by being deliberate about them you can mitigate the risk that the tester poses. I've got lots examples of techniques for each perspective and I'd love to tell you all about the perspectives and the techniques."
