Estimating bugs in order to get better at estimating
A while ago I posted about why I feel you shouldn’t estimate bugs. In a nutshell, if you estimate bugs you’ve essentially ‘double-dipped’ the feature. There’s the estimate for the feature and the estimate(s) for the bug(s) introduced while the feature was being built. If you’re using Scrum defects go to the top, they don’t get estimated and they get worked on until the technical debt is gone. In Scrum, quality is not negotiable so if you’re...
Read MoreTo Estimate Bugs or to Not Estimate Bugs, that is the question
Is it a bug or is it an improvement? Well, that debate will happen during any project but the purpose of this post is to iterate why bugs (legit bugs) should not be estimated in Scrum. First of all, if you’re using Agile development techniques, you shouldn’t have any bugs to begin with but in the event bugs are introduced in a project, according to Scrum, they float to the top of the product backlog and take priority over all other work. Quality is not negotiable. So to answer...
Read MoreGet Lean Change
