Slides from my session at Agile Testing Days USA 2019 #AgileTDUSA2019 DevOps has expanded the opportunity for testers to become arbiters of quality. I'll share 3 core responsibilities of testers in DevOps: to know, protect, and verify. I'll establish a working definition of Quality Ownership and discuss its relationship to Product Ownership to help testers look beyond deriving quality from executing tests and shift instead towards becoming quality owners. Helping testers to find their path to enabling continuous quality, through pairing and sharing test ownership across the team while instilling value from pull request to production.

1. Panoramic
Quality
Brendan Connolly
@theBConnolly || http://brendanconnolly.net
Sr. Quality Engineer, Procore Technologies, Santa Barbara CA

2. @theBConnolly
Panoramic
Quality
Brendan Connolly
@theBConnolly || http://brendanconnolly.net
Sr. Quality Engineer, Procore Technologies, Santa Barbara CA

3. What’s So Different?
@theBConnolly

4. @theBConnolly
SPEED
Orders of Magnitude
Risk / Release Inversion

5. Continuous
@theBConnolly
Delivery TestingIntegration

6. @theBConnolly
OWNERSHIP
Developers Devour All

7. @theBConnolly
Our Landscape
Is Changing

8. Core Responsibilities
@theBConnolly
Protect VerifyKnow

9. Regions of
Responsibility
@theBConnolly

10. @theBConnolly
Customer

11. @theBConnolly
Know => Customer
Application & Audience
=> Application Expertise
=> Persona / Permission Boundaries
=> Interactions & Motivations

12. @theBConnolly
Protect => Customer
Feature Corruption
- When adding functionality for one group
of users affects others NEGATIVELY
- Not a regression because it’s a new/
additive change.

13. @theBConnolly
Protect => Customer
Feature Flags
=> You need it in production does your
customer?
=> Do all of your customers?

14. @theBConnolly
Protect => Customer
Change Tolerance
=> Instability is indistinguishable from rapid
change

15. @theBConnolly
Verify => Customer
Test In Production
If a bug is production but no customers can
access it, is it still a bug?

16. @theBConnolly
Verify => Customer
User Analytics
=> It’s not just about catching errors
=> Instrument to measure effects and
usage

17. @theBConnolly
Architecture

18. @theBConnolly
Know => Architecture
The Geography of Software
=> How it’s built / deployed
=> Where it’s running
=> How it solves your customers
problems

19. @theBConnolly
Know => Architecture
Environmental Impact
=> Local, Staging, Production
=> What Works Where?
=> What Doesn’t?

20. @theBConnolly
Protect => Architecture
Boundaries of Risk
=> Boundaries of components can be
borders between developers

21. @theBConnolly
Verify => Architecture
Minimum Viable Environment
=> Work as close to home as you can
=> Take the Developers local changes
=> Identify tests

22. @theBConnolly
Verify => Architecture
Health & Wellness
=> Monitoring
=> Surfacing information

23. @theBConnolly
Code

24. @theBConnolly
Know =>Code
Topography
=> how the pieces fit together
=> how data flows

25. @theBConnolly
Know =>Code
Streets & Neighborhoods
=> Find your way around
=> Know the Rough Areas
=> Where “stuff” goes down

26. @theBConnolly
Know =>Code
Talk Me Thru Your Changes
=> Know the story behind the code
=> Be a the sounding board
=> How do unit tests reflect the change?

27. @theBConnolly
Protect =>Code
Code is Protected by Tests
Not Testers
=> Unit Tests are a foundation for quality

28. @theBConnolly
Verify =>Code
Influencer vs. Influenced
=> When Works as Designed doesn’t work?
=> Who’s saying the tests are built right?

29. @theBConnolly
PAUSE

30. Embracing
Ownership
@theBConnolly

31. @theBConnolly
Let Go of Testing
https://danashby.co.uk/2016/10/19/continuous-testing-in-devops/

32. @theBConnolly
Quality Ownership

33. @theBConnolly
Product Ownership
- Define the product backlog
- Groom and prioritize the backlog
- Ensure completed user stories fulfills the
acceptance criteria
https://medium.com/@melissaperri

34. @theBConnolly
Product Ownership
Focused On:
- Features, Market, Schedule
Goes Deep On:
- Domain, Competition, Planning

35. @theBConnolly
Quality Ownership
Focused On:
- Features, Value, Safety
Goes Deep On:
- Application, Customers, Planning

36. @theBConnolly
Quality Ownership
Support ObserveSteward

37. @theBConnolly
Quality Ownership
Stewardship:
- An ethic that embodies the responsible
planning and management of resources.
- the responsible overseeing and protection
of something considered worth caring
for and preserving

38. @theBConnolly
Quality Owner => Steward
Product => steward of what will be
built
Quality => steward of what has been
built

39. @theBConnolly
Quality Owner => Stewardship
Quality is in Your “Charge”
Responsibility for controlling or caring
for something
A formal statement accusing someone
of committing a crime

40. @theBConnolly
Quality Ownership=> Support
Open Source your Mindset
=> Be an #ALLY for testing
=> Enable & Mentor Quality
=> Infuse Quality into automation

41. @theBConnolly
Quality Ownership=> Support
Supporting Quality
Testing

42. @theBConnolly
Quality Ownership=> Support
Avoid Pyramid
Obsession
=> Pyramids aren’t models
of efficiency
=> Quality isn’t in layers

43. @theBConnolly
Quality Ownership=> Support
Testing Cathedral
=> Your app is central
=> Counter-balance risk
with efficient supports

44. @theBConnolly
Quality Ownership
Observability:
- measure of how well internal states of a
system can be inferred from knowledge
of its external outputs

45. @theBConnolly
Quality Ownership=> Observe
Continuous
Feedback
Virtuous cycle of
better observability Source: https://medium.com/@copyconstruct

46. @theBConnolly
Quality Ownership=> Observe
Continuous Collaboration
=> Build skills to break down barriers to
collaboration

47. Quality Ownership
Hands on Code
Hands on Customer
Supporting a pipeline of
Quality from pull request
to production

48. Be Well, Connect,
Share
http://bit.ly/own-quality
Connect With Me
Twitter / LinkedIn : @theBConnolly

49. 49