Modèle d'interruption
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.
Temps estimé pour ce cours: 12 minutes
Audience: Intermédiaire
Prérequis suggérés: Backlog de produit, Product Owner, Backlog de sprint
À l'issue de la formation, vous serez en mesure de
Voir les diapositives du cours
[slideshow_deploy id='7234']
Product Owner Aperçu :
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 valeur commerciale. 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 Procédure d'urgence, aborting the Sprint.
Papiers et motifs
Le Scrum Pattern Language of Programing : Le mouvement PLoP codifie des pratiques agiles bien connues qui ont été mises en œuvre avec succès à de nombreuses reprises.
Papiers :
Teams that Finish Early Accelerate Faster: A Pattern for High Performing Teams
6 méthodes agiles pour accroître l'engagement des salariés
Les organisations qui utilisent des méthodes de travail agiles enregistrent une amélioration de l'engagement de leurs employés. Engagez, équipez et responsabilisez vos employés.
French 
English 
Spanish