DEV Community

Discussion on: The ONE chart every developer MUST understand

Collapse
 
sebbdk profile image
Sebastian Vargr

It works in my immediate surroundings, i managed to get several old complex systems refactored by doing it, the business value here being increased application performance and feature output.

I remember distinctly one place where we took bugs quite serious. We had a hard limit of ~15 bugs of varying severeties, any more than that and bugs would get higher priority relative to new features.

It was quite efficient, after implementing it, we definitely had less bugs on production.

I'm not sure if it was the measuring of just the proper focus they received that did the thing, but it definitely did something.

Thread Thread
 
bosepchuk profile image
Blaine Osepchuk

That's great. I'm glad it worked for you.

I've tried to be a "nudger" too and it definitely helped by my projects also suffered from some of the 36 classic mistakes so we never went as far and as fast as I would have liked.