Are you flexible with the order you do the work (i.e. Cancelling a sprint)?
7/01/2016 12:05 PM by
Every now and then your clients are going to want to change their priorities and have you work on something which they see as more important than some of the items in your current sprint. Provided that it doesn't have any negative effects overall, there isn't any reason why you can't stick to the "customer is always right" philosophy.
So what will you do when this happens?
Double check that this new item is more important than the current sprint items (if not add it to the product backlog instead)
- Add the new PBI to the current sprint
Remove another item of similar size off the sprint and back to the backlog
In the rare case where the entire sprint goal and all PBIs are no longer high priority, you can instead cancel the entire sprint and start again:
- Move any left over work/items to the backlog.
- Send a debrief to the client with a note e.g. As per your request we have just cancelled Sprint five and will start on Sprint six. The remaining items have been moved into the backlog.
- Send a Sprint Forecast for the new sprint
This should only be done in extreme circumstances as it is traumatic to the team.
Do you feel this rule needs an update?