Quality And The Squad Framework

Overview and high level analysis of Spotify's Squad framework with emphasis on the adoption of the framework at SumUp and the impact on Quality Assurance.
It was presented at DEV.BG's QA meet up.

Transcript

1. Quality And The Squad Framework
2. 2 Aneta Petkova Local QA Chapter Lead @
3. 3 What do we do?
4. Part I: The “Scrum company” What we know, and what we don’t
5. 5 The QA The Dev2 The PO The Dev1 The Master
6. And so they lived happily ever after. 6 Until they didn’t.
7. What went wrong? ✘ PO didn’t respect scope ✘ Developers gave wrong estimations ✘ QA was always late
 ✘ Scrum teams are often divided by tech components while ✗ Business features spans multiple components 7
8. 8 Who’s afraid of the spaghetti code monster?
9. How did we get here? Let’s take a step back! 9
10. What is SCRUM? An implementation of the Agile methodology 10
11. Agile A set of principles that aims to improve the process of software development; A mindset. Agile vs. Scrum Scrum A framework that helps teams to apply the agile principles into their daily work. 11
12. Scrum is NOT: ✘ A synonym of Agile ✘ Going to work unless you understand Agile ✘ Replacement of organisation structure 12
13. Berlin 13 Distributed Locations Sofia Sao Paulo Cologne
14. So we looked for a true master 14 Images by Derek Laufman
15. So we looked for a true master 15 Images by Derek Laufman
16. Part II: The “Agile company” In theory and practice
17. Spotify’s Squad Framework Squad Small cross- functional self- organised team Chapter Competency area, such as QA Tribe Group of squads working in same business area Guild A community of interest with no obligatory character
18. Tribe Tribe Chapter Chapter Squad Guild
19. Why? 19 Image from https://lifemadesimplebakes.com Autonomy Alignment
20. 20 Ehm… But what about Quality?! Autonomy Alignment
21. The QA Side of things 21 ✘ The automation team ✓ Automation QAs and Devs in every squad Automation Guild
22. The QA Side of things 22 ✘ The automation framework ✓ Each squad has own framework and/or tools Autonomy > Reusability
23. The QA Side of things 23 ✘ QA vs. Dev ✓ Quality and speed are squad responsibility “Done is better than perfect” - Sheryl Sandberg
24. Engineering Growth 24 ~40 people 2016 ~80 people 2017 ~150 people 2018 ~20 people 2015
25. And then we went to Stockholm A complex idea can be conveyed with just a single still image, namely making it possible to absorb large amounts of data quickly. 25
26. To discover many changes ✘ The chapters have all but disappeared ✘ Squads now have tech leads ✘ QA as a role is gone ✘ “We have only one environment and it’s called production” ✘ Testing is transferred to alpha users as much as possible 26
27. But we’re on the right path ✘ Autonomy is still above all ✗ 7 different HTTP implementations! ✘ QA autonomy within squads ✘ To learn fast, fail fast ✘ No rules, just great examples 27
28. Part III: The takeaway(s) To keep or not to keep
29. 29 There is no “one size fits all” solution
30. 30 Image from https://lifemadesimplebakes.com Autonomy Alignment
31. THANKS! Any questions? You can find me at: • aneta.petkova@sumup.com ✘ anetavp ✘ apetkova 31
32. Credits Special thanks to all the people who made and released these awesome resources for free: ✘ Presentation template by SlidesCarnival ✘ Photographs by Unsplash ✘ Icons and images from freepik 32