Should we write user stories for bugs?

When we come across a bug during the sprint we are bit confused and doubt about whether to add a user story for it or just fix it without recording. Let’s look and an explanation given by Mike Cohn (One of scrum guru) regarding this matter,

There are three types of defects that we find during a sprint.

1. Defects that should be fixed immediately

2. Defects that should be fixed within the sprint but not immediately

3. Defects that cannot be fixed within the current sprint

Defects that should be fixed immediately are often related to current work. Therefore it is not required to add them to sprint backlog or product backlog as that should be immediately fixed. That sense not required to add user stories for this type of defects.

For the defects that should be fixed within the current sprint should be added to the sprint backlog but not to the product backlog.

Defects that cannot be fixed within the current sprint probably be added to the product backlog.

Please note that when adding defects to the sprint backlog or product backlog, it is not required to write it as a user story. That is with the syntax of ‘As a….I want to …So that …’ As long as defect is understandable for all the developers and stakeholders you can use natural language to record defects.