Managing bugs using an e2e philosophy

Fresh ideas to move your company culture from hundreds of bugs to a minimum

I would like to show you how a detected problem is managed in one of the most important European FinTech companies, where around 50 tech engineers are supporting more than 1000 operational users.

I will share the evolution of our bugs workflows and how we have changed our philosophy till nowadays, moving from more than a hundred bugs to less than 15 opened bugs for our main projects.

Given we apply an end-to-end philosophy to our daily work, teams are responsible from user story creation through it is delivered, working and supported after release too. It means that if a bug is detected in Production (it doesn’t matter if it was detected by final users, quality members or other technical folks) it will be escalated to an assigned Agile team and depending on the complexity and the urgency of this issue, it could be treated in the current Sprint, the next one, or as a hotfix in order to be deployed as soon as possible.

In this session I will list our automated quality gates executed during the SDLC of a bug, and how we can make important decisions based on our bugs metrics


More Related Sessions


Full-Day Tutorial (6-hour Workshop)

9:00-17:00

Practical Ethics for Tech Teams

45-minute Keynote

17:45-18:30 Room F1

The challenges ahead

30-minute Talk

11:55-12:25 Room F3 - Track 3: Talks

Team-Driven Microservice Quality Assurance

120-minute Workshop

10:25-12:25 Room D3+D4 - Track 4: Vendor Talks

A Tester’s Guide to Unit Testing

Equipment required

If you like AgileTD you might also be interested in :