Yes. I don’t subscribe to the idea that bugs don’t belong on the backlog with everything else.
You can separate into two different backlogs (bugs and features) but you still need to pick from both.
If you don’t keep them on a backlog then people will start arguing whether something is a bug or in fact a feature request/missing functionality. That is a waste of time.
If you get a bug report for a bug that will take a week to fix you need to “assign story points” to it (in the sense that if you commit to fixing it you will at least know you have a week less available for something else!). Fixing the bug becomes a prioritization between the bug and adding features. So the bug is measured in the same units as features and prioritized against features. And fixing the bug adds value too - if you have feature X not working and you make it work, that is value. If you fix X instead of implement new feature Y you deliver value with feature X instead of feature Y. Does that value not count because it was “implemented before”? If you fix bugs for a month and ship a new version with only bug fixes then that is zero new features yes. Your velocity can be counted in terms of “new features” and be zero. Or “rate of fixing bugs” and be high (it’s still a good measurement for knowing whether you have enough resources to hit a goal such as a yearly release - which might be planned with 50%
bug fixes and 50% new features!).
If you don’t keep them on a backlog then people will start arguing whether something is a bug or in fact a feature request/missing functionality. That is a waste of time.
If you get a bug report for a bug that will take a week to fix you need to “assign story points” to it (in the sense that if you commit to fixing it you will at least know you have a week less available for something else!). Fixing the bug becomes a prioritization between the bug and adding features. So the bug is measured in the same units as features and prioritized against features. And fixing the bug adds value too - if you have feature X not working and you make it work, that is value. If you fix X instead of implement new feature Y you deliver value with feature X instead of feature Y. Does that value not count because it was “implemented before”? If you fix bugs for a month and ship a new version with only bug fixes then that is zero new features yes. Your velocity can be counted in terms of “new features” and be zero. Or “rate of fixing bugs” and be high (it’s still a good measurement for knowing whether you have enough resources to hit a goal such as a yearly release - which might be planned with 50% bug fixes and 50% new features!).