| Context | A Scrum Team is in the Sprint Planning meetings. |
| Problem | The Development Team needs deliverables or services from collegues outside the team but the same organization to realize the Sprint Goal. If a self-organized Development Team has successfully negotiated a Sprint Goal with the Product Owner and requires support, deliverables or services from outside collegues, the team cannot rely only on itself anymore. These collegues are called “dependencies”. If the dependencies are not committed on the forecast of the Development Team for the Sprint, the chances to reach the goal are reduced. |
| Forces | too little/too much organizational overhead |
| Solution | The dependencies commit on the Sprint Goal Build a second group of people around the Development Team for the Sprint consisting of those collegues, which need to contribute to the Sprint for the Sprint Goal to be reached. They need to be part of the Sprint Events and fully support the Sprint Goal as well as the forecast. These “Committed Dependencies” will organize their work around the commitment to support the Sprint Goal and become part of the Sprint instead of creating the need for additional management effort. The Development Team needs to plan the forecast with the dependencies, so that they can commit. |
| Resulting Context | The Scrum Team and the Committed Dependencies can meet the Sprint Goal by relying on self-organization. |
Dieser Artikel wurde von Andreas Heilwagen am 01.08.2011 um 07:36 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.
