The document describes an interrupt buffer that was originally created by Jeff Sutherland and updated by Nigel Thurlow. The interrupt buffer is an allocation of story points in the current sprint that can be used for new stories from the product backlog or approved requests. The product owner acts as a gatekeeper and decides what requests the team works on, with approved items entering the buffer. If the buffer is overflowed, it means the team's velocity has been exceeded and the sprint goal may not be met, requiring a re-plan of the sprint.

1. The Interrupt Buffer
Original Idea by Jeff Sutherland
Updated by: Nigel Thurlow
Last Updated: August 16th
2015
Version: 2
Support Requests
Manager Requests
Product
Backlog
8
8
5
5
5
3
5
3
3
5
5
5
3
Sprint
Backlog
8
5
5
5
3
Kaizen
Buffer
Sales Requests
Do Later Low Priority
5
4
3
2
1
5
4
3
2
1
A
B
C
The buffer is an allocation of points in the current Sprint that can be consumed by new stories from the
backlog, or by extraneous requests that have been expressly approved by the Product Owner.
A The Product Owner is the gatekeeper for the team, and filters all requests for team time regardless of source. The
PO, and only the PO decides on what the team should work on. Items he allows through the gate enter the buffer.
On Buffer overflow, Abort Sprint, Re-Plan, Slip Dates. Overflowing the buffer means you cannot meet your
Sprint Goal as you have consumed too much velocity from the team.
B
C Buffer
Product Owner