Bugs, those pesky errors that you didn’t foresee.
As defined by Wikipedia, a bug is:
… an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways.
Scrum, the process we all know and (some) love.
As defined by the the creators, Scrum is:
… a simple framework for effective team collaboration on complex software projects.
What isn’t so well defined is when and how to document a bug whilst working in Scrum.
Most people will agree that bugs should be documented somewhere; the simplest being on a piece of paper, the more advanced being in an issue management system such as Bugzilla or JIRA.
Should you then document every bug you find during a sprint? I don’t think so, in fact I think doing so can be detrimental to your team.
Let’s look at the definition of a bug