The document discusses the evolving expectations in software development and the changing roles in quality assurance, particularly in teams without dedicated testers. It emphasizes the importance of customer feedback in ensuring product relevance while not relying on them for correctness, and highlights the speaker's multifaceted role in fostering a quality-oriented culture. The document also addresses skill diversity in teams and the significance of balancing specialized expertise with general skills to maximize delivery value.

1. Testing with no Testers
Alan Page

2. The way people use software is
changing

3. Expectations for software are
changing

4. Do we need to change the way we
make software?

6. - Started Testing in 1993
- Lots of products, lots of roles
- Titles: Test Architect, SDET, Director of Test Excellence, etc.
- Joined current team in July, 2015
- “Software Engineering” Team (no testers)
- I’m the DQP (Designated Quality Person)
- Combination of many roles
- More on what I do day-to-day later
About Me

7. I Know What You’re Thinking…

11. Champions of Quality

16. Agenda:
- Theory
- Practice
- Discussion

17. Theory

18. Customer “testing”

19. Customer Quality
(Telemetry data,
sentiment analysis,
beta, etc.)
“ilities” – Performance,
Reliability, Security, World
Readiness, Usability, etc.
Functional Quality
Code Quality (correctness) / Hygiene
Processes / Practices / Culture

20. So…do we rely on customers to test
our software?

21. Don’t rely on customers to make sure
your product is correct.
But by all means, rely on them to make
sure you made the right product.

22. Who “owns” Quality?

23. What Is Quality?

24. “Quality is value to some person”
- Jerry Weinberg

25. If “some person” is the customer…

26. Who “owns” creating value for the
customer?

27. Practice

28. - Still a hole filler
- Part Test Manager, part Test Architect, part Release Manager
- My responsibilities:
- Build a quality culture
- Ensure we follow quality processes
- Don’t let things fall through the cracks
- Some examples:
- Code Reviews
- Quality horizontals
- Teaching testing
- The quality process
My role on a tester-less team

29. Skill Diversity is Important Critical

31. Specializing Generalists
Generalizing Specialists
Everyone doesn’t do everything…
…but the team contains “all of the skills”

32. By staffing a team with people who have an
area of expertise, but can do anything, you
can maximize the value of each delivery
cycle
-Scott Selhorst

34. Dev “stuff”

35. Project
Management
“stuff”
Dev “stuff”

36. Dev “stuff”
Project
Management
“stuff”
The
“Remainder”

37. Data Science
Exploratory Testing
“The Remainder”

40. Before I Go…

43. You’re Not As Different As You Think

44. Questions / Discussion
http://angryweasel.com
http://angryweasel.com/ABTesting

45. Thank You
http://angryweasel.com
http://angryweasel.com/ABTesting