Interrupts happen. In computing, an operating system has to be able to handle interrupts or the machine will crash. It’s the same with Sprints. The key to handling interruptions is to expect them.
Estimated time for this course: 12 minutes
Suggested Prerequisites: Product Backlog, Product Owner, Sprint Backlog
Upon completion you will:
View Class Slides
Product Owner Overview:
That's the ideal. However, there are often times, when interruptions are unavoidable. Real time feedback can be essential for creating a quality product but it needs to be regulated to protect the Team from getting mixed messages and slowed down. In a perfect world, that feedback would be incorporated into the Product Backlog for future Sprints, but there are times when it simply isn't possible to wait.
Read More on the Interrupt Pattern
Second, when an unplanned task surfaces the Product Owner orders it in the buffer according to business value. The most important thing is to take a deep breath and realize that many requests can be put off to the next Sprint, but the critical interrupts that cannot wait go into the buffer.
The Interrupt Pattern is a tool that protects the Team from unreasonable exceptions. If it is obvious the interrupt buffer is going to overflow the Product Owner should immediately activate the Scrum Emergency Procedure, aborting the Sprint.
Papers and Patterns
The Scrum Pattern Language of Programing : The PLoP movement codifies well know Agile practices that have been successfully implemented many times.
Teams that Finish Early Accelerate Faster: A Pattern for High Performing Teams