The document discusses ways for a development team to improve quality without hiring a separate QA team. It suggests focusing on perfecting the existing team by improving their responsibility, awareness, and communication. For responsibility, it recommends practices like code reviews and demonstrations. For awareness, it discusses using techniques like test-driven development and retrospectives. And for communication, it proposes standup meetings, demonstrations, and having developers support users to understand real needs. The overall message is that quality can be increased by teaching developers these skills and ensuring they take accountability through questioning and changing practices.

1. Pavel Gabriel
coach, programmer, agile-evangelist
alovak@gmail.com
Monday, October 11, 2010

2. Successful development
without QA team
By CharlotteSpeaks♥{Charlotte.Morrall}
Monday, October 11, 2010

3. Your dev team doesn't
provide sufficient product
By Gabriel Pollard
Monday, October 11, 2010

4. Boss says: several testers
will solve our problems
Monday, October 11, 2010

5. You don't want extra
departments and processes
Monday, October 11, 2010

6. ?
Hire testers
or Perfect the team?
Monday, October 11, 2010

7. More than 90% of tester jobs
require technical skills
Monday, October 11, 2010

8. C/C++/J2EE/Perl/Ruby/
Python/Network
Monday, October 11, 2010

9. You'd like to increase quality
to make your boss happy
Monday, October 11, 2010

10. You decided to perfect the
existing team
Monday, October 11, 2010

11. Monday, October 11, 2010
?
How?

12. 1 2 3
Responsibility Awareness Communication
Monday, October 11, 2010

13. 1
Responsibility
Monday, October 11, 2010

14. ?
Problems with responsibility
Monday, October 11, 2010

15. Who is responsible for the
quality?
Monday, October 11, 2010

16. Whole team is responsible
Monday, October 11, 2010

17. You are responsible
Monday, October 11, 2010

18. How to make developers more
responsible?
Monday, October 11, 2010

19. Teach the developers to be
responsible
Ask
ques)ons
Monday, October 11, 2010

20. One day...
Monday, October 11, 2010

21. What are you going
to do about it?
-­‐
I’m
but
one
developer
Monday, October 11, 2010

22. What change can you make?
-­‐
I
can
help
colleagues
Monday, October 11, 2010

23. So, what are you going to do?
-­‐
I
will
prepare
presenta)on
Monday, October 11, 2010

24. Practices
to
boost
responsibility
Monday, October 11, 2010

25. Code review
Monday, October 11, 2010

26. Demonstrations
Monday, October 11, 2010

27. 2
Awareness
Monday, October 11, 2010

28. Monday, October 11, 2010
?
Problems with awareness
Developers
are
tolerant

29. Underperformance
Monday, October 11, 2010

30. Bugs
Monday, October 11, 2010

31. Bad communication
Monday, October 11, 2010

32. Aware developers can cope
with any problems
Monday, October 11, 2010

33. Teach the developers to be
awareness
Ask
ques)ons
Monday, October 11, 2010

34. One day...
Monday, October 11, 2010

35. Why did you fail to do that?
-­‐
I
could
not
test
Monday, October 11, 2010

36. Why did you write this kind of
test?
-­‐
We
have
been
always
tes)ng
such
way
Monday, October 11, 2010

37. What else can you do?
-­‐
I
don’t
know
Monday, October 11, 2010

38. What could help you?
-­‐
I
need
suitable
tes)ng
tool
Monday, October 11, 2010

39. What are you going to
do about it?
-­‐
I’m
going
to
find
it
and
use
it.
Monday, October 11, 2010

40. Practices
can
complement
ques)ons
Monday, October 11, 2010

41. TDD/BDD
Test
Driven
Development
Behavior
Driven
Development
Monday, October 11, 2010

42. ATDD
Acceptance
test-­‐driven
development
Monday, October 11, 2010

43. Retrospectives
to
improve
process
and
discover
tools
Monday, October 11, 2010

44. 3
Communication
Monday, October 11, 2010

45. ?
Problems with communication
Monday, October 11, 2010

46. What does a developer need?
to
do
his
work
effec)vely
Monday, October 11, 2010

47. Vision
purposes,
target
audience,
use
cases
Monday, October 11, 2010

48. Knowledge
peculiari)es
of
business
domain
per)nent
stories
Monday, October 11, 2010

49. Feedback
Monday, October 11, 2010

50. Practices
to
improve
communica)on
Monday, October 11, 2010

51. Standup meetings
Monday, October 11, 2010

52. Company meetings
to
see
internal
processes
and
needs
Monday, October 11, 2010

53. Demonstrations
to
get
a
feedback
Monday, October 11, 2010

54. Support done by developers
to
understand
real
needs
and
problems
of
the
users
Monday, October 11, 2010

55. 1 2 3
Responsibility Awareness Communication
Monday, October 11, 2010

56. Monday, October 11, 2010
?Questions?
Pavel
Gabriel
alovak@gmail.com

57. Thank you!
Monday, October 11, 2010