It’s Never a Technology Problem: Using Experience to Solve the Problem
summary
Argues that failed projects come from process and people not tools, with concrete failures: the ArriveCAN smartphone requirement that blocked snowbirds at the border, teams dumping test cases into Jira or hiring contractors to build brittle UI automation, and orgs installing Jenkins/TeamCity without stable tests or environments. Shows practical fixes: draw current pipelines, use a test automation pyramid to pick which tests to automate, and run mind map and exploratory test charters with diverse team members.
AI-written summary · about
chapters (14)
- 0:00Introduction and speaker intro
- 1:12Career journey and experience
- 8:31Bias and assumptions in tech
- 11:02Technology evolution and fundamentals
- 13:55Using experience to solve problems
- 16:43Technology serving people
- 19:37Common process problems
- 23:51Visualizing and solving problems
- 27:26Non-technical solutions
- 31:01Automation and teamwork
- 34:11Continuous delivery workflow
- 37:00Slowing down to solve problems
- 38:44Diversity and collaboration
- 40:31Q&A session
related talks
01h 22mAgile - The Road Towards Organizational Agility - Progress & Challenges Examined
20mWorking with Others and Delivering as a Team — Bridges Seen Through Human Relationships
34mHow test engineers with collaborative & growth mindset are winning
27mTechnical Excellence: Why does it not stick even now?
50mAsaf Shochet Avida, Eitan Noy: Why My Amazing Test Automation Project Crumbled
30mThis is Not a Technology Problem: Leveraging Culture and Process to Make the Most...
42mOpening Keynote: Blunders in Test Automation
49mWelcome to the Future! Preparing for our Agile Testing Journeys