title: deploying mid-sprint with scrum (large ongoing 'brownfield' public web projects)
body: <p><a href="https://rads.stackoverflow.com/amzn/click/com/0130676349" rel="nofollow noreferrer" rel="nofollow noreferrer">Schwaber &amp; Beedle's 'scrum' book</a> (and the other scrum literature I've read) seems to focus on having a releasable product by the end of the sprint. Web development for an established site (at least in our case) consists of developing 'enhancements' (of various sizes) and many small 'fixes'. Deploying (to web) only at the end of the sprint would slow down our deployment of large enhancements (probably a good thing) but would dramatically slow down our deployment of small enhancements and fixes (i.e. the bugs hang around longer).</p>
  
  <p>Are mid-sprint deployments heretical in scrum? Are sprints even applicable in our case? Have I misunderstood sprints entirely?</p>