| | |
| Context | The Scrum Team is in a Sprint, but frequent interrupts result in the Sprint goal constantly being missed. |
| Problem | Scrum Teams are usually interrupted in their Sprints by short term requests, changes in priorization or problems. These interruptions are often cause by management or the Product Owner and cannot be foreseen during the Sprint Planning meetings. |
| Forces | too little/too much organizational overhead |
| Solution | Create a limited interrupt buffer and abort the Sprint when it is overrun. Interrupts cannot be avoided, so plan them based on your best estimate. Assign the management of the interrupt buffer to the Product Owner and pipe all interrupts through his priorization. If the requested interrupts exceed the interrupt buffer, abort the Sprint. When management support for this rule is ensured, nobody will be glad to kill a Sprint and the requests will get under control. |
| Resulting Context | The Sprint goals are achieved and costs for interrupts are transparent. |
Weiterführende Informationen
Dieser Artikel wurde von Andreas Heilwagen am 13.07.2011 um 08:00 gepostet und unter Scrum eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.