“Quality at Speed” is Atlassian’s approach to QA, and we are constantly evolving what that means and how it translates to actual dev team processes. Our developers can confidently take on testing activities, while our QA Engineers tackle larger, harder, and bolder challenges. Teams can ship better features, faster, and reach ambitious quality improvement goals. We'll talk about how our team has embraced this mindset, how this changes our role in dev teams, and the results we want to achieve. We'll cover the different ways that quality can be defined, the importance of fast deployments, and how we work with teams like DevOps, Growth and Customer Insights to help our dev teams and ultimately benefit our users. Products covered: JIRA Software, Bitbucket, Bamboo

1. MARK HRYNCZAK • CLOUD QA MANAGER • ATLASSIAN
The future of QA
at Atlassian

2. Quality at speed
Our mission

3. WHAT DOES QUALITY MEAN?
SHIP FASTER
HOW TO DO LESS TESTING
RECAP
Agenda

4. WHAT DOES QUALITY MEAN?
HOW TO DO LESS TESTING
RECAP
Agenda
SHIP FASTER

5. Ship faster

7. Hello!
My name is
AGILE

8. Keep calm
and let me help you

11. Like Dislike

12. Would you recommend
Quality Assistance to your colleagues?
0
8
16
24
32
40
0 1 2 3 4 5 6 7 8 9 10
Detractor Neutral Promoter

13. Mentor
Help create quality-aware
developers
Monitor
Surface the data showing
quality (or lack of)
Educate
Teach how to spot risks and
avoid pitfalls
Improve the dev team

14. SHIP FASTER
HOW TO DO LESS TESTING
RECAP
Agenda
WHAT DOES QUALITY MEAN?

15. What does “quality” mean?

16. Hierarchy of needs
Self-
actualization
Esteem
Love/belonging
Safety
Physiological

17. Hierarchy of quality
Successful
Useful
Usable
Performant secure
Deployable functionally ok

18. Hierarchy of quality
Successful
Useful
Usable
Performant secure
Deployable functionally ok

19. Hierarchy of quality
Successful
Useful
Usable
Performant secure
Deployable functionally ok

20. Atlasssian Performance Monitoring Header

21. Hierarchy of quality
Successful
Useful
Usable
Performant secure
Deployable functionally ok

22. NPS

23. NPS

25. Hierarchy of quality
Successful
Useful
Usable
Performant secure
Deployable functionally ok

27. Basic
Stop shipping serious bugs
Useful
Find out if users love/loathe,
and why
Successful
What is your department
trying to achieve?
Define quality goals

28. WHAT DOES QUALITY MEAN?
SHIP FASTER
RECAP
Agenda
HOW TO DO LESS TESTING

29. How to do less testing

30. Detection
Finding issues after
development through
testing.
Prevention
Stopping issues
from being committed
or developed.
Mitigation
Reducing or eliminating
the impact of an issue.
Eradication
To completely remove an
issue or class of issues.
How to do less testing

31. Detection

32. Prevention

33. Mitigation

34. Eradication

35. Prevent
Identify potential problems
before coding
Mitigate
Reduce the impact of
problems to end users
Eradicate
Make it impossible for
problems to exist
Do less testing

36. WHAT DOES QUALITY MEAN?
SHIP FASTER
HOW TO DO LESS TESTING
Agenda
RECAP

37. Do more with less

38. Solve the right
quality problems

39. Do less testing

40. Wrap-up

41. Thursday, 11:30-12:10pm

42. MARK HRYNCZAK • CLOUD QA MANAGER • ATLASSIAN
Thank You!