Send us Fan MailIn this episode of The Agile Software Engineering Deep Dive, we take a field trip into software engineering memory lane.Modern software teams have better tools than ever: CI/CD pipelines, cloud platforms, automated testing, observability, feature flags, and now AI assistants. But better tools do not remove the need for engineering discipline.This episode revisits a set of older or half-forgotten practices that still ask very relevant questions: Zero Bug Bounce, Zero Bug Strategy, Definition of Done, Entry and Exit Criteria, Code Freeze, Bug Triage, Root Cause and Defect Escape Analysis, Regression Test Strategy, Usability Lab Testing, and Performance Testing.The purpose is not to bring back old bureaucracy. It is to recover the practical engineering questions hidden inside these practices.Are we stabilizing? Are known defects visible? Does done really mean done? Do we understand what our bugs are teaching us? Do we know what must never break silently? Are users actually able to use the product? And do we detect performance degradation before it becomes failure?Modern tools can help us move faster and with better evidence.But they do not remove the need to ask the right engineering questions.Support the showThis Podcast is an audio version of the written Agile Software Engineering newsletter. If you want to go deeper, don't forget to subscribe the newsletter too.
More episodes of the podcast Agile Software Engineering
We do not know your name or where you live, but the map says you were here. Thank you for stopping by — every flag below is someone who came to say hello.