5. Solving trivial bugs
1. Developer writes code and tests
2. Tester finds defect and logs
3. Developer tries to reproduce
4. Developer finds bug and investigates
5. Team discussion about how it should work
6. Developer re-codes, re-unit-tests, re-builds,
re-delivers
7. Tester verifies and closes ticket
6. We let bugs happen
Requirements
Software
Bugs
Development
Quality
Control
7. Requirements Maturity
Three Amigo meeting
Acceptance Driven
Development
We need change!
In Flight UI Review
Pair Programming
Quality Without
compromise
Constant Feedback
Deliver Value
13. Requirement maturity
Testable and estimable?
User Story short enough?
UI elements defined?
Business rules defined?
Customer acceptance Tests defined?
15. Three Amigos meetings
Discover unknowns
What does the requirement mean?
What are the special cases?
How will we test this?
What about the non-functions?
What to do with errors?
16. Deliver value in stead of Huh?
Burning Tasks We’re getting
wet…
Plan Build Test Review Deploy
31. Quality comes from within
Commitment
Continuous
Improvement Quality Responsibility
Confidence
32. Working together
Exploratory Testers Programmers
Communication Communication
Be curious about how stuff
is tested by Programmers Ask Testers for help
Partner with Programmers Show Testers what’s
build / tested
Coach Test Awareness /
Test infection Help out with
Automation
33. What are we doing here?
It’s NOT Testing
It’s NOT Coding
....
