Feed the Starving Sprint

When you introduce Scrum in an organization that is used to the more traditional way of developing software, a common scenario is that your product backlog is reduced faster than it is filled with requests for new features. The reason for this is that Scrum enables the team to deliver functionality more effective than the receiving organization is used to, hence it takes too long to get the new functionality into production. What happens then is that you will probably end up with a a sprint that slowly starves to death. The medicine for this is as simply as work as hard you can to getting the new functionality into production as fast as possible. This is the only way to force the end users to actually use the new functionality and come up with suggestions for improvements to feed the sprint…

Leave a Reply

Your email address will not be published. Required fields are marked *