What is an Agile Tester?

Transcription

1 Consultant What is an Agile Tester? Colombo Agile Conf, June Father Agile & Lean coach Author

2 Agile tester mindset 00:22

3

4

5

6 Case study: Game development company Game backlog 8 Design-ready games 15 Production-ready games 12 1m Concept pres. 4h 6m Actual work: 3 months Time to market: 25 months Resource planning 1d Graphics design Sound design Dev Test & deploy 1w 6m 6m 1m 3w 3m 3w (1m+2m)

7 Before Game backlog 8 Design-ready games 15 Production-ready games 12 1m Concept pres. 4h 6m Actual work: 3 months Resource planning 1d Graphics design Sound design Dev 1w 6m 6m 1m 3w 3m (1m+2m) Integr. & deploy 3w Time to market: 25 months After Cross-functional game teams Game team (graphics, sound, dev, test, deploy, etc) 7 times faster Time to market: 3-4 months Better games Less Planning More fun

8 Cross-functional teams I m fast! 6 months We re slow! Joe Dave Lisa Release 3 months Joe We re alot faster! Dave Lisa Release I m a bit slower January February March April May June July 9

9 Test phase Test tea m Tester role

10 Test phase Req Code Test

11 We own quality Test tea m Programmers Testers

12 I own quality Tester role Tester Dev team

13 Role Competency We own quality Cross-functional development team QA = Quality Assurance = Quality Assistance

14 Roles DB Design GUI Backend Test

15 Competencies DB Design GUI Backend Test

16 Knows a bit about many things Cross functional team Doesn t mean everyone has to know everything Knows a lot about one thing Product Backlog I can do Java, but I m not so good at it. Lisa Skills Needed to implement Top X backlog items Java DB Web Test Domain CM I m good at Test! I don t know CM at all. But I m willing to learn! Joe Fred Jenny David Erik I won t even go near a database!

17 ensure How do you know that your product works? Who are the stakeholders? 1. Understand the problem What need do they have, that we want to solve? How will we know when we ve solved it? How will we know if we re moving in the right direction? 2. Iterate until you ve solved it Minimize the distance to MVP Deliver, measure, adjust continuously

18 Typical activities 00:22

19 Make sure backlog items are testable & valuable As a buyer I want to save my shopping cart so that I can continue shopping later How to demo: 1) Enter store 2) Put a book in shopping cart 3) Press save cart 4) Leave store, and enter it again 5) Check that the book is in my cart

20 Find defects early! Cost of defect $ Age of defect

21 Sit with the developers Developers Developers & Testers Testers Meeting room

22 Shorten the feedback loop 5 Maker People (# of handoffs) User # of handoffs Time (Feedback delay) minutes hours days weeks months years Length of feedback cycle

23 Push for Continuous Delivery Automatic Build Test & integrate Deploy to staging Deploy to prod Manual Code & commit Manual test

24 Create a shared vocabulary Unit Test? Integration test? Quality? Acceptance test? Technical debt?

25 Set working agreements for test automation Each user story has at least one black-box acceptance test AT and UT complement each other Acceptance tests: coupled to UI, decoupled from internal design Unit tests: coupled to internal design, decoupled from UI Complex code has unit tests Almost all code is covered by SOME kind of test (AT or UT) We know which code isn t covered and have a good reason for it

26 Do & teach exploratory testing!?

27 Done includes no added technical debt Backlog Ready for dev In progress Ready for production - No added tech debt

28 Example: Test automation backlog Step 1: Decide what needs to be tested Change skin Security alert Transaction history Block account Add new user Sort query results Deposit cash Validate transfer

29 Step 2: Classify each test Pay every time Pay once Test case Risk Manual Test Cost Automation Cost Change skin Security alert Transaction history Block account Add new user Sort query results Deposit cash Validate transfer low 0.5 hrs high high 1 hrs high med 3 hrs low high 5 hrs low low 0.5 hrs low med 2 hrs medium high 1.5 hrs low high 3 hrs medium

30 Step 3: Sort the list Test case Risk Manual Test Cost Block account high 5 hrs low Automation Cost Automate first! Validate transfer high 3 hrs medium Transaction history med 3 hrs low Sort query results med 2 hrs medium Automate later Deposit cash high 1.5 hrs low Security alert high 1 hr high Add new user low 0.5 hrs low Change skin low 0.5 hrs high Don t bother automating

31 Example: Tech backlog Product backlog Tech backlog

32 Reserve X% of team capacity for the tech backlog Product backlog 80% Sprint Tech backlog 20%

33 Example: Spotify 00:22

34 Play Everywhere! Like a magical music player in which you ve bought every song in the world!

35 >400 people in tech Gothenburg Stockholm San Francisco New York 36

36 > 50 squads

37 Autonomous Squad Cross-functional, co-located, self-organizing team

38 39

39 Squads are grouped into Tribes Tribe Tribe Tribe Tribe Tribe Tribe

40 Each Tribe is a lightweight matrix focused on delivery Vertical = Delivery. Horizontal = knowledge sharing & personal development Tribe Tribe Chapter Chapter Chapter Guild Chapter

41 Reality is messy

42 Decoupling to enable frequent releases Client App squad!#? Feature squads

43 Self-service model Client App squads Infrastructure squads Enable & support IOS Android Desktop Web Feature squads Enable & support Enable & support

44 Release trains & Feature toggles

45 Failure Recovery is more important than Failure Avoidance Failure Avoidance Failure Recovery

46 Limited Blast Radius via decoupled architecture

47 Limited Blast Radius via gradual rollout

48 Trust > Control 100% control = 0% motion If everything s under control, you re going too slow! - Mario Andretti

49 A/B stats Idea/Problem Narrative & Prototypes & Metrics Build MVP Radio you can save! Follow your favorite artist Tweak Deploy Analyze data

50 Example: Big Government Project 00:22

51 Team structure - before Requirements analyst team 3 Development teams Test team! #%! #%!?!? 52

52 Next 10 Ideas Features features Development System test User acceptance test Production 53

53 Team swimlanes Next 10 features Dev in progress Ready for sys test Sys test progress 54

54 Team swimlanes Next 10 features Dev in progress Ready for sys test Dev Team 1 Dev Team 2 Dev Team 3 55

55 Daily cocktail party 9:15 10:15 56

56 10:00 10:15 Project sync 9:45 10:00 9:45 10:00 Test sync Requirements sync Dev sync 9:30 9:45 9:15 9:30 9:30 9:45 Feature team 1 Feature team 2 Feature team 3 57

57 Example: Measuring velocity by counting cards Count cards Velocity per week 58

58 Example: Release planning using a burnup chart All of these will be done Tota l # of delivered features Week Some of these will be done, but not all None of these will be done 60

59 Oh no, bottleneck in System Test! FLOW 61

60 Tech stories Next 10 features Next 5 tech stories 62

61 Bottleneck Let s stop building new features... and focus on test automation! 63

62 Everyone doing tech stories 64

63 Top 3 recurring bugs 65

64 Definition of ready for development Definition of ready for system test 66

65 67 67

66 Before: Test at end Test Fix Release Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Now: Test continuously Release Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Test Fix Test at end: Test continuously: %&@#! Test Fix Time saved! 68

67 Bug fixing process Bug found! Blocker? No Yes Write sticky-note, find developer, fix now! More important than any of the current top 30? No Ignore it Yes Replace one of the other top 30 bugs with this one Don t log it. Fix it NOW! 69

68 Three input queues Next 10 features Next 5 tech stories Next 5 lower priority bugs 70

69 Wrapup 00:22

70 What is an Agile Tester? An agile team member with testing expertise Helps the team become quality-aware... and learn how to deliver better stuff

71 Mindset Quality Assurance Manual test Functional test Requirements Late involvement Long feedback loop Find defects Quality Assistance Automatic test Exploratory test Customer needs Early involvement Short feedback loop Prevent defects

72 Agile is a direction, not a place The important thing isn t how you work. The important thing is how you improve the way you work!