A client recently asked that I change our project management so that we run our one month scrum, then stop development activity. The pause was to allow the team to be available to help with support and user adoption, asses, then determine what to take from the product back log and begin the next sprint.
It’s easy to move faster than the user community, and if several dozen new features and functionality pile up without adoption, the result is that it is quite possible the real objective has not been met. I like this idea of scrum 'pacing', although it makes planning staffing more challenging.
