I really like the idea of picking up the bugs when they are still fresh and to pick up the essential ones immediately.
But why not have a list of non-essential bugs just in case, it's a slow Friday afternoon.
I also think that non-essential bugs are nice stories for a new team member to pickup. A good way to get up to speed with the codebase.
And in the end all bugs are essential. How can there be a bug that never needs attention and can be discarded?
Yeah, I guess you can keep it out of your backlog itself but keep them on the s ide. So you have some nice-to-have improvements for indeed, those slow friday afternoons or new developers that can get their teeth into the codebase with some issues that are not so daunting.
I don't agree that all bugs are essential. Fixing bugs requires work - I have a finite amount of work that I can expend on the product that I am building. I can choose between fixing a bug that affects 0.5% of my customers resulting in 20% of them failing to convert that is a 0.025% conversion impact for me. Let's say my average revenue per transaction is $1000 then this bug has a 2.5c per transaction impact.
Alternatively I can use that same time to build some new functionality that that I have tested and looks good for a 50c - $1 positive impact on revenue per transaction.
There is no way I consider that bug "essential" until such time as my next most valuable piece of work is less valuable than 2.5c per transaction.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I really like the idea of picking up the bugs when they are still fresh and to pick up the essential ones immediately.
But why not have a list of non-essential bugs just in case, it's a slow Friday afternoon.
I also think that non-essential bugs are nice stories for a new team member to pickup. A good way to get up to speed with the codebase.
And in the end all bugs are essential. How can there be a bug that never needs attention and can be discarded?
Yeah, I guess you can keep it out of your backlog itself but keep them on the s ide. So you have some nice-to-have improvements for indeed, those slow friday afternoons or new developers that can get their teeth into the codebase with some issues that are not so daunting.
I don't agree that all bugs are essential. Fixing bugs requires work - I have a finite amount of work that I can expend on the product that I am building. I can choose between fixing a bug that affects 0.5% of my customers resulting in 20% of them failing to convert that is a 0.025% conversion impact for me. Let's say my average revenue per transaction is $1000 then this bug has a 2.5c per transaction impact.
Alternatively I can use that same time to build some new functionality that that I have tested and looks good for a 50c - $1 positive impact on revenue per transaction.
There is no way I consider that bug "essential" until such time as my next most valuable piece of work is less valuable than 2.5c per transaction.