@davemurdock Escape is a really common term in software as well. It just means that a bug or defect made it through the testing process without being discovered. I’ve worked places where the term was only applied if the issue was discovered by customers in a shipped release as well as places that applied it to issues that made it into unreleased/internal builds. Escapes usually cause reflection on and updating of the testing process.
@davemurdock Maybe! Some quick searching suggests it’s an Agile thing, but I would have thought its origins were older. Certainly the first team I worked on that used it is older than the Agile Manifesto, tho it’s possible we started using the term around that time (2001).
@davemurdock The first team I was on that used it was in CA but not “doing Agile” (tho I would argue that our process was more agile than other teams I’ve worked on that ostensibly were). I don’t think the east coast teams I worked on used it, so maybe you’re right that it’s a west coast thing.
@lorihc a toast 🍺🍹 🍷 ☕️ 🥤 to as few “quality escapes” as we can all manage in 2024
@lorihc I started doing agile around 2003 in CA & I don’t remember that term, but there a lot of stuff from then I don’t remember 😅 Been East Coast again near 20 years & doing agile continuously, never heard from multiple trainers and coaches 🤷🏼♂️