Welcome to the Future! Preparing for our Agile Testing Journeys
summary
Teams report learning to test APIs with curl, automate iOS UI and debug JavaScript with Chrome devtools by pair‑programming and reading; a team of three testers and ~15–16 programmers uses exploratory testing charters assigned to developer pairs, runs a hack week where generative tests find an elusive crash and produce a reproducible failure, and uses impact mapping and story mapping to discover business goals and the minimum viable product. Continuous integration, visibility and small experiments guide risk‑focused testing.
AI-written summary · about
chapters (12)
- 0:00Start
- 0:16WELCOME TO THE FUTURE!
- 4:33THE AGILE TESTER
- 8:41YOUR CONTEXT
- 13:36Distributed teams
- 18:47Or story mapping
- 23:08SO, WHAT MAY NOT WORK IN THE FUTURE?
- 26:05BUSINESS VALUE
- 29:21Uncertainty
- 34:57CAN WE PREDICT THE FUTURE?
- 38:10NEW HORIZONS
- 40:44THE WORLD AS IT IS...
related talks
34mHow test engineers with collaborative & growth mindset are winning
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
49mChanging Testing Culture in a Ginormous Company
46mIt’s Never a Technology Problem: Using Experience to Solve the Problem
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
01h 05mAdding value in an agile context
30m"Timbits"
54mTech Truth: Agile Evolution & the Future of SW Engineering