In Scrum, we put a priority on creating high-performing teams. You've probably heard that phrase a hundred times with regard to Scrum. Unfortunately, while we certainly have the best intentions when it comes to creating a high performing team, we often develop habits that do everything BUT create high performance (we'll talk about some of these bad habits in other tips). One of the worst things we can do to our teams is allow them to work on too many things at the same time (see this tip for more information). Another real productivity killer occurs when we allow too many changes to the content of the Sprint after the Sprint has been planned.
Scrum does, in fact, provide for the modification of Sprint content after the Sprint has been started. It requires everyone on the team to modify the Sprint content because it was everyone on the team that agreed to the Sprint content in the first place. That's only fair, right? If a content change is necessary, we should definitely do it (particularly if it results in higher productivity for the team). However, we should, at the same time, limit how often we change Sprint content. Here are some reasons why:
Take our advice, while Scrum does allow for the change of content in a Sprint, avoid making changes to in-progress Sprints unless it is absolutely necessary. When organizations "honor the Sprint," teams tend to perform better.
Copyright © 2016, Artisan Software Consulting LLC