Fiverr - delivering fast w/ no QA - Agile Israel 2016 Gil Wasserman
This document discusses Fiverr's approach to quality assurance called "NoQA" where QA is removed from the critical path of software development in order to allow for faster delivery of features. Some key aspects of Fiverr's NoQA approach include: - Removing QA from being a gatekeeper and instead integrating QA as part of the development team - Relying on developers to test their own code through techniques like unit testing and deployment to staging environments - Focusing on continuous monitoring of production systems to identify issues once features are live - Guiding principles of trust, autonomy, ownership and accountability to replace formal QA processes - Embracing uncertainty and continuous learning as software development is viewed as an ongoing knowledge game
Fiverr - delivering fast w/ no QA - Agile Israel 2016 Gil Wasserman
- 1. Delivering Fast. Then Faster. No Retreat. No Surrender. No QA. Gil Wasserman Fiverr VP R&D Agile Israel 2016
- 3. About Fiverr
- 4. Quick Facts About Fiverr • Founded: 2010 • Funding: $110M • Team: 250 • Dev team: 70 • Offices: Tel Aviv, NYC, SF, Chicago, Miami
- 5. Fiverr is the world’s largest marketplace for creative and professional services with millions of buyers and sellers around the world.
- 6. Logo Design, Illustration & Caricatures, Video & Animation, Copywriting and more! Work Created on Fiverr Creative Goldmine
- 9. 25 Million Orders Order processed every 4 seconds; Over 1M orders per month
- 10. CD Daily Production Deploys Deploys Done by Developer Task Force: PM, BE, FE, BA, Designer 20 TFs Micro Tasks, Large Projects Team X 5 Millions LOC No QA !
- 11. NoQA - Why QA in The Critical Path Is a Drag Is a Drug Is a Barrier to Self Growth Software Development is a Knowledge Game
- 12. NoQA - For What Removing QA from The Critical Path Faster Delivery Efficient Effective Better Quality Does It Fit All ?
- 13. Section A First Steps: Learn to walk Think small No context switch. QA not a Gatekeeper a Team Member QA Starvation Use your judgement No Bugz Manag. 15 → 50→ 70 Dev 2 → 2 → 0 QA Learn to Forget
- 14. Hey...What About Automation? • UT vs Integration vs full system tests ? • Environment - Local, staging, p-likes • DOM load vs full rendering? • UT - Essential quality tool or a waste? • Automated testing development - a bottleneck or not? • Successful run - a condition to merge? • Cross Browsers? • Refactoring?
- 15. Guiding Principles • Company Vision and Mission • Dev Mission: Quality Impact, Fast! • Nothing is perfect. Everything is imperfect. Grow within uncertainties. • Minimal policy setting • Trust → Autonomy → Ownership → Accountability • Fear is no option. Be Responsible. Use your judgement • Continuous learning • Continuous goal setting HubSpot
- 16. So... What About Automation? • UT vs Integration vs full system tests ? • Environment - Local, staging, p-likes • JS or full rendering? • UT - Essential quality tool or a waste? • Automated testing development - a bottleneck or not? • Successful run - a condition to merge? • Cross Browsers?
- 17. Own the Journey Own the Feature Understand the user Own the Feature Live in Production Own the Business Production Health Own the Business Followup - Graphite, Grafana - Kibana - Graylog - Seyren - CircleCI - Slack - Docker, Consul - Impala - SiSense - P-Likes - New Relic - Rollout - Feature flags - AB tests MVR, MVA
- 18. Rule Your Domain • Tech and Product ownership ○ Teamwise ○ Enabler not a Tyrant ○ Managing tech debt ○ Code health ○ Production health “Devs know their code best and should test it.” Large project retrospect
- 19. Our Current Quality Pyramid Cup Manual Local Testing UT Manual P-Like Testing Rollout Strategy Production Monitoring/Alerts Quick Turnaround Judgement Call
- 20. Is It Right For Me?
- 21. Thank you