Hi all,
Here is the illustration of the problem.
Our client is legacy company and they have few hundred bugs in the product backlog. They also new story as part of the product backlog.
And some of those bugs has "highest" priority.
So the PO and scrum team, agree to fix "X" number of bugs and "Y" number of stories in each sprint.
And the release of the next version is done every quarter (not after each sprint).
The method (or units) of estimation is # of person-days.
They have not estimated the bugs , while the " Fix version number is assigned to the bug" (Fix means target version). But without having the estimate it is becoming difficult to predict the "scope / content" of the next release. Upper management would like to know , how many defects will be "released" while the next version is delivered to the clients.
So the question is :
Shall we do estimates for the bugs (efforts in person-days) ? OR don't estimate for bugs?
I think this is more of a discussion than question as there is really not "right" solution, just the one that works for you.
I have used the following approaches:
Either way, if you wish to be serious about beating down the bug backlog you need to account for it and set expectations for each developer. Discuss w/ your team to see what works best for them.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dipak,
in my opinion you only need to estimate those that you think might do this sprint and maybe a handful of others. Otherwise you are wasting effort.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.