The question is - ‘Is it ok to size bugs and consider it like any other story while calculating capacity, When bugs would be planned for successive sprints?’
When I entered in to a team recently I found them not sizing their bugs. But I personally thought that bugs should be sized.
Why because,
When I entered in to a team recently I found them not sizing their bugs. But I personally thought that bugs should be sized.
Why because,
- ·Those bugs are of huge effort
- Then only we can identify the actual effort
- ·Then only we can identify the capacity
- ·Then only we can ensure if all our metrics related to effort, capacity and normalized capacity are correct.
- ·They claim credit for stories which are having MINOR defects with the approval of PO.
- ·Any defects reported at last few days of sprint are moved to next sprint without sizing.
- ·Both PO and SM are in agreement with Team to fix the issues without credit.
However I am not a purist. An purist- Agilist working on offshore model? Laughingstock.
Still, there is a limit and degree for compromises. So, I investigated and understood the reason why they are not sizing bugs.
But, what I noticed was, somehow the team had forgotten that such a conditional compromise is accepted only for MINOR, last minutes bugs.
I am still working with this team to ensure that efforts beyond a degree should be sized.
But, beyond which degree? That’s something the team to decide and the PO to be in agreement.
What if they won’t do this? Then they will never know their capacity and normalization
Ideally, the team should strive to deliver without defects.
