![Yes!
Does the team own UI/Experience?
QA?
Backend
Front end BFF
Stream-aligned Team [Checkout]
Stream-aligned Team
[Products]](https://image.slidesharecdn.com/qa-share-250326034000-f6f81cea/85/Is-there-a-place-for-QA-in-autonomous-fast-flow-teams-81-320.jpg)
Is there a place for QA in autonomous fast flow teams?
- 1. Is there a place for QA in autonomous fast-flow teams? Sheen Brisals Consultant. Author. AWS Hero
- 2. COVID-19
- 4. Meet Charlie Name: Charles Education: B Eng (Software) Experience: 5 Years Skills: Computer nerd!
- 5. Interview Me: Could you explain your way of working with the QA? Charlie: Erm... Sorry, there is no QA in our team! Me: Oh! Who does QA? Charlie: All the engineers do! Signal 1
- 6. Post-COVID
- 9. Chat Me: So, Luke, do you need a senior or mid QA? Luke: Me: Erm, what do you mean? Luke: We can operate without a QA! I think... neither! Signal 2
- 10. Agenda 1.QA: Then & Now 2.Team Autonomy 4.Blockers & Shifts 3.Fast Flow Operation
- 11. sheen-brisals sheenbrisals sbrisals.medium.com #TheServerlessBook #TheSpeakerBook Independent Consultant O’Reilly Author AWS Serverless Hero Team Topologies Advocate Sheen Brisals leanpub.com/TheSpeakerBook
- 12. No QA was made redundant while preparing this talk! disclaimer
- 13. 1. QA: Then & Now
- 14. What is Quality? Fitness for Use!
- 15. Material: Steel Build: Handcraft Packaging: Recycle Delivery: Sustainable Specification Characteristics Product
- 16. Quality Planning Material Build Packing Delivery Quality Assurance QC QC QC QC Quality Planning Quality Assurance Quality Control Covers customers, requirements, tools, processes, etc. Prevents errors with measures, standards, processes, etc. Checks against quality requirements at process output.
- 17. SQA Software Quality Assurance Software industry’s adaptation of the industrial QA process!
- 18. Requirements Analysis Design Coding Testing Release Maintenance SQA SQE Assurance Engineering Principles Procedures Protocols Responsibility of conducting QA process Software Testing The Waterfall Development Model
- 19. 2. Team Autonomy
- 20. Big Teams Credit: lavilo-webdesign.com Bigger Problems
- 22. Cognitive Load Source: Balancing Coupling in Software Design
- 23. If you can’t feed a team with two pizzas, it’s too large! Jeff Bezos, Founder, Amazon 2-Pizza Teams
- 24. • Communication • Collaboration • Decision-making • Iterative development • Incremental delivery • Improved velocity • Innovation • And many more... 2-Pizza Teams
- 25. 2-Pizza Teams Product Manager Engineering Lead Engineers (Devs) Data Engineer(s) UX Designer(s)
- 28. QA Involvement Ideation Analysis Design Development Testing Release Operation Next Iteration / Increment Every activity is a team activity QA engineer is part of every activity Modern Development Model
- 29. DevOps You build it, You run it! Dr. Werner Vogels, CTO, Amazon.com
- 30. DevOps Movement Ideation Analysis Design Development Testing Release Operation Next Iteration / Increment Every engineer can release Every engineer can operate
- 31. Domain: Ecommerce System Boundaries With DDD Subdomain: Products Subdomain: Customer Subdomain: Orders Subdomain: Loyalty Bounded Context BC BC BC BC BC BC Bounded Context BC BC
- 32. An approach to organizing business and technology teams for fast flow. Team Topologies
- 35. Domain: Ecommerce True Autonomy Subdomain: Products Subdomain: Customer Subdomain: Orders Subdomain: Loyalty Bounded Context BC BC BC BC BC BC Bounded Context BC BC
- 36. Dev Prod Test Pre- prod Autonomous Team Payments - Bounded Context Cloud Operation Owns Operates Autonomous Team: Development & Operation
- 37. Recap Big teams + complex systems experience high cognitive load. Independent & agile teams promote the distribution of QA. Autonomous teams own, develop, and operate their systems. QA & development engineers participate in all processes.
- 38. 3. Fast Flow Operation
- 39. Iterative & Incremental Ideate Design Build Operate Iterate Test Credit: www.pacific-research.com/
- 41. Iterative, Incremental, Automation Ideate Design Build Operate Iterate Test
- 43. Iterative, Incremental, Automation, & Value Ideate Design Build Operate Iterate Test
- 46. Agile Autonomous Teams • Multiple engineers release multiple increments every day! • Anyone can deploy to prod! • Friday is like any other day!
- 47. Dev Prod Test Pre- prod Autonomous Team Payments - Bounded Context Cloud Operation Owns Operates Autonomous Team: Development & Operation
- 48. Authoriz ation Pay by Link Cancel Refunds Capture Audit Service Data Gateway Fraud Preventi on Notifica tions Reports Payments - Bounded Context Autonomous Team: Multiple Pipelines Data Gateway Refunds Pay by Link Commit Build Test Stage Release
- 49. 4. The Blockers
- 50. The QA Gate Commit Build Test Stage Release aka QA Sign-off
- 51. The QA Gate Commit Build Test Stage Release
- 52. The QA Gate Commit Build Test Stage Release Cognitive Load
- 53. The QA Gate Small incremental changes for the Developers, but collectively high load for a QA. Cognitive Load
- 54. The PR Gate Commit Build Test Stage Release Dear QA, Please test and approve the changes in my PR (pull request) so that I can merge. Thanks!
- 55. The PR Gate Value Stream Impact End-to-end pipeline: 1 hour Wait for QA: 1 day
- 56. 5. The Shifts
- 57. The Shared Responsibility Model • Cloud • Security • Sustainability
- 59. Autonomous Teams & Multidisciplinary Engineers Understand stakeholder requirements Propose architectures Compose microservices Implement single-purpose functions Cloud & Serverless Engineers Incorporate security measures Employs the observability measures Deploys and operates services Design data model and event schema
- 60. Autonomous Teams & Multidisciplinary Engineers Understand stakeholder requirements Propose architectures Compose microservices Implement single-purpose functions Cloud & Serverless Engineers Incorporate security measures Employs the observability measures Deploys and operates services Design data model and event schema Also, write enough tests!
- 61. The Shift in Patterns
- 63. If the traditional QA approach was to find bugs, the modern approach is to prevent bugs!
- 64. Shift in the Mode of Tests Automated Tests Manual Tests
- 65. Does a distributed event-driven system have two distinct ends?
- 66. Shift in the Types of Tests Unit tests Load tests Integration tests End-to-End tests Performance tests Contract tests
- 68. In cloud and serverless applications, not all business logic is in function code!
- 70. Testing strategies for cloud and serverless mostly originate from software engineers - not QA engineers!
- 74. Maximizing stability limits how fast features can be developed and how quickly products can be delivered, and dramatically increases their cost, which in turn reduces the number of features a team can afford to offer.
- 75. The Square of Balance Test Release Recover Observe
- 76. The Square of Balance Quality Stability vs Speed Test Coverage vs Test Coverage Observability vs Criticality Recoverability vs
- 77. Recap In a fast flow team environment, QA sign-off acts as blocker. Bug prevention is a priority for modern fast flow teams. Test, release, observe, and recover – balance them well. QA requires almost the same cloud/serverless skills as Devs.
- 78. Do You Need a QA?
- 79. QA? A. Yes! B. No! C. Maybe! D. It Depends! E. All of the above!
- 80. Does the team own UI/Experience? QA? Backend Front end BFF
- 81. Yes! Does the team own UI/Experience? QA? Backend Front end BFF Stream-aligned Team [Checkout] Stream-aligned Team [Products]
- 82. Yes! Do you share your codebase? Shared Codebase push pull clone add commit branch checkout merge Staging Test Develop Prod QA?
- 84. Yes! Highly regulated environment? QA? Reduce Risk Prevent Breach
- 85. Recap Yes – UX and interactive applications. Yes – Shared codebase and cloud accounts. Yes – Business domain with unclear boundaries. Yes – Highly regulated environments.
- 86. To Close…
- 87. In enterprises one size does not fit all. To move fast and make things, you must be willing to experiment. Ideas and experimentation are vital to identifying the appropriate developmental practices and team dynamics for success!
- 88. Who is bold to experiment?
- 89. sheen-brisals sheenbrisals sbrisals.medium.com #TheServerlessBook #TheSpeakerBook Independent Consultant O’Reilly Author AWS Serverless Hero Team Topologies Advocate Sheen Brisals Thank You! leanpub.com/TheSpeakerBook