How I became a tester!
summary
Claims that cross-functionality works here with concrete steps: teams use Jenkins and Git, developers pair to copy or write Java tests, a missed initialization breaks CI and forces shared learning; Python integration scripts take two sprints to finish but ship; a track factor of one motivates spreading skills until redundancy reaches two or three; company creates a T-shaped Community of Practice, runs pairing, spikes and coffee-corner sessions, and accepts short-term slowdown to gain lasting resilient teams.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:47About me
- 1:47Fishbowl
- 6:02Scrum
- 6:47Breaking Silos
- 7:35Meeting Almudena
- 8:04Testing ceremonies
- 9:10Track factor
- 10:13Agile team
- 17:12Continuous integration
- 19:56Common goals
- 22:51Tshape
- 26:00Change
- 28:33Culture
- 33:51Learning time
- 36:34Celebrate
- 39:51Questions
- 50:48Soft Skills
related talks
51mWhy Companies Without Testers are the Best Place to Be One
15mThe Tester I Was and the Tester I Could Be
51mHow I lost my QA job
55mTest Management Revisited
49mChanging Testing Culture in a Ginormous Company
34mHow test engineers with collaborative & growth mindset are winning
53mHow Testers Add Value to the Organization But also, to ourselves
41mMartijn Goossens: Be a Better Test Friend to Your Team