If you’re in bed with your partner but you’re not collaborating, then nothing good is going to come of it. You don’t have the same vision, you lose sight of what needs to be done and the end result is likely to be poor quality and, of course, disappointing. The same can be said for Quality Assurance (QA), and testing in development projects. Fully incorporating testing into your project from the start is essential to cross-team collaboration - after all, only by maintaining interaction between development and testing can you ensure a quality and secure end-product. So rather than leave testing to the end, we say get into bed with QA from the beginning - for a lasting relationship that keeps both you, and your client, smiling.

1. Get into bed with QA
(and keep testing agile)
simply brilliant thinkers
making software brilliantly simple

2. Hi!

3. Why am I here today?

4. The great
DIVIDE

5. Right?

6. Nope.

7. - The product will have problems
- The testing will be late
- Changes will be more expensive

8. Developers vs Testers

9. Developers vs Testers

10. “Thrown over
the fence”

11. “Thrown over
the fence”

12. Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

13. test PLAN

14. plans CHANGE

15. plans CHANGE

16. CODE TEST
FEEDBACK

17. - INDIVIDUALS
- INTERACTIONS
- COLLABORATION

18. - INDIVIDUALS
- INTERACTIONS
- COLLABORATION

19. About those battlelines?

20. About those battlelines?

21. INTEGRATION

22. INTEGRATION

23. Let’s decide...
● At what points will we all come
together?
● How are we going to maintain
collaboration?

24. “Collaborative mindset”

25. At what points will we all come together going forward?
> Daily standups

26. At what points will we all come together? > Standups
● What did you do yesterday?
● What are you doing today?
● Any blockers in your way?

27. At what points will we all come together?
> Daily standups
> Ticket kick offs!

28. At what points will we all come together? > Ticket kickoffs
1. What is the change?
2. Do we have acceptance criteria?
3. Is the ticket complete? Aka does the ticket have all the relevant
information for development and testing to begin work?
4. Will automated/manual test scripts be completed as a part of the
work?
5. Have we made any assumptions?
6. Do we need any more detail from the client?
7. Are you comfortable enough in your understanding of the area to
start working on the ticket or is a handover required?

29. At what points will we all come together?
> Daily standups
> Ticket kick offs!
> Storytime

30. At what points will we all come together? > Storytime
“Introducing the
Three Amigos”
- Ryan Thomas Hewitt

31. At what points will we all come together? > Storytime
Business analysts:
Requirements
Acceptance criteria
Developers:
Code
Unit tests
QA:
Scenarios
Test cases

32. Let’s decide...
● At what points will we all come
together?
● How are we going to maintain
collaboration?

33. How are we going to maintain visibility and collaboration through the
project life cycle?
> Transparency

34. How are we going to maintain visibility and collaboration through the
project life cycle? > Transparency

35. How are we going to maintain visibility and collaboration through the
project life cycle?
> Transparency
> Owning decisions

36. How are we going to maintain visibility and collaboration through the
project life cycle? > Owning decisions

37. How are we going to maintain visibility and collaboration through the
project life cycle?
> Transparency
> Owning decisions
> Get the most out of retros

38. How are we going to maintain visibility and collaboration through the
project life cycle? > Get the most out of retrospectives

39. So...

40. Building a
COLLABORATIVE MINDSET

41. Time. Passion. Results.

42. Continuous feedback loop

43. Continuous feedback loop

44. Less “my”, more “our”

45. Less “my”, more “our”

46. KEEP IT UP!
Review. Adapt. Collaborate. Repeat.

47. Reduced product
problems and risks
= Happy team

48. Reduced product
problems and risks
= Happy team

49. A QA Tester is
for life…
not just for the
end of a project

50. With
CONTINUOUS COLLABORATION
Comes
CONTINUOUS QUALITY

51. Cheers!
Questions?

52. www.boxuk.com
@boxuk.com
/sophie-hayden-63722192
@thesophiehayden