title: Best ways to fit bug fixing into a Scrum process?
body: <p>I have been studying and reading about Scrum in the last few days and reading about Sprint Planning and tasks. One problem that popped into my mind is how to deal with bugs in Scrum. Henrik Kniberg lists some ways of dealing with this issue in his very nice book <a href="http://www.crisp.se/henrik.kniberg/ScrumAndXpFromTheTrenches.pdf" rel="noreferrer">Scrum and XP from the Trenches</a> :</p>
  
  <ol>
  <li>Product owner prints out the most
  high priority Jira items, brings
  them to the sprint planning meeting,
  and puts them up on the wall
  together with the other stories
  (thereby implicitly specifying the
  priority of these items compared to
  the other stories). </li>
  <li>Product owner creates stories that refer to Jira
  items. For example “Fix the most
  critical back office reporting bugs,
  Jira-124, Jira- 126, and Jira-180”.</li>
  <li>Bug-fixing is considered to be
  outside of the sprint, i.e. the team
  keeps a low enough focus factor (for
  example 50%) to ensure that they
  have time to fix bugs. It is then
  simply assumed that the team will
  spend a certain amount of time each
  sprint fixing Jira- reported bugs </li>
  <li>Put the product backlog in Jira
  (i.e. ditch Excel). Treat bugs just
  like any other story.</li>
  </ol>
  
  <p>Is this really something that needs to be decided per-project basis or are there better solutions? I can think of problems with each of those approaches. Is there a hybrid coming from those approaches that works best? How do you handle this in your projects?</p>