title: In agile development how do you deal with the "less-well-architected" code that results from a sprint-focussed mindset
body: <p>I work on an agile project using Scrum.</p>
  
  <p>Sprints have come and gone and we have fulfilled milestones successfully. The system works well enough to meet the current customer requirements. </p>
  
  <p>However, we are left with a system in serious need of refactoring, as much of the development was performed with little eye on the future (instead the focus was on the sprint at hand).</p>
  
  <p>How best to deal with this? Sprint(s) dedicated to refactoring?</p>