How testers can be a liability
@ulrikama

Ulrika Malmgren

How to prevent testers from being a liability
@ulrikama

Misconceptions about testers
and testing
Testers break stuff
@ulrikama

Myth!
Programmers can't test their own code
@ulrikama

Myth!
Some programmers lack practice at testing
More accurate:
3 factors
which affect quality
@ulrikama

Quality of the conversations
@ulrikama


@ulrikama

Temperature reading - Virginia Satir
Measuring collective intelligence - MIT
The five keys to a successful Google team - Google
https://rework.withgoogle.com/blog/five-keys-to-a-successful-google-team/
Read more
So what?
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


So what?
Techniques for identifying 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

So what?
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

3 factors which affect quality
@ulrikama




See testers as ambassadors for quality
@ulrikama

Raise the knowledge level of your team
Reflect on communication
Work with understanding
Sharpen your tools
How to prevent testers from being a liability
By Ulrika Malmgren
How to prevent testers from being a liability
@cukeup 2016 - 2016-04-14
- 1,732