I’ve had to explain all of the points MPJ makes in this video, many, many times. Now I can just send a link to this video. And while I tend to call out e2e tests as their own thing, deep down they’re really integration tests.
I’m part of a distributed team that has daily stand-ups and other meetings, that are all online. Thus, I can’t watch this video without laughing my ass off…
To paraphrase Jon’s list of 5 “crazy ideas”:
- Don’t track bugs; just fix them
- Delete all bugs in your backlog that you can’t fix immediately
- All newly reported bugs are either rejected or fixed immediately
- Automated tests are created for each new bug
- Set WIP limit for bugs (eg. 20 total)
Ten years ago I would have scoffed at the idea of not tracking bugs and deleting the bug backlog, but today, I can see this as a realistic possibility. In fact, this isn’t far from how my current team operates today. So what’s stopping me from going all in? Guts?