| Context | The Development Team has finished a Sprint and the Scrum Team wants to improve their processes. |
| Problem | How to improve processes on a regular basis with successful execution of changes? Improving processes is traditionally done by assessments and planning/implementation of improvements, driven by a dedicated quality management team. The continuous improvement cycles are long and execution of the agreed changes fails or does not deliver the desired results in many cases. |
| Forces | too little/too many changes too little/too much stability |
| Solution | Establish a Sprint Retrospective. One of the common methods to organize a Sprint Retrospective is to ask for lowlights and highlights of the Sprint and then discuss possible improvements as well as assigning responsible persons to ensure, that the improvements are implemented. Running through the continuous improvement cycle every few weeks helps to fix processes step by step without many big bang-style changes. The dicussion engages the Scrum Team and by moving responsibility for solutions from a dedicated quality management team to the Scrum Team, acceptance of the changes is higher than in other scenarios. |
| Resulting Context | The Scrum Team is ready to start the next Sprint with improved processes. |
Dieser Artikel wurde von Andreas Heilwagen am 04.05.2011 um 08:30 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.
