Back to Forum

How to handle a showstopper production bug?

Last post 07:33 am July 3, 2018 by Neeraj Pandey
4 replies
Neeraj Pandey
11:00 am July 2, 2018

Hi All

If a bug is found after the release then ideally a User Story should be created and should be taken up in the coming sprint. However if the bug is a showstopper then how to send a fix for the same and stay within the boundaries of scrum?

Thanks

Ian Mitchell
02:01 pm July 2, 2018

What impact do the Development Team think the defect would have on the Sprint Goal if it were to be actioned and fixed?

What impact would there be if it wasn’t fixed?

Neeraj Pandey
03:42 pm July 2, 2018

Hi Ian

If the bug is not fixed then one feature will be unsuable.

And if this bug is fixed as an emergency fix then it will take 1 day so, the current Sprint is impacted by 1 day of work. 

How to proceed in this situation?

Should the fix be done right away ?? The product owner wants it to be fixed within 24 hrs.

Please guide 

Thanks

 

 

 

Ian Mitchell
07:18 pm July 2, 2018

Do the team actually have a Sprint Goal which would be impacted by this defect and whether or not it is fixed?

If there is no Sprint Goal then the rules of Scrum are not being applied.

My advice would be to fix the defect in this instance, and to hold a retrospective afterwards to see how the team’s implementation of the Scrum Framework might be improved.

For teams which are implementing Scrum, the Bradley Bug Chart can be a useful guide to deciding when to fix defects:

http://www.scrumcrazy.com/file/view/ScrumBug-613.pdf

 

Neeraj Pandey
07:33 am July 3, 2018

Thanks Ian

Bradly Bug chart is very useful.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.