| Context | The Development Team cannot realize all Sprint Backlog Items as additional work has been detected and documented as new Technical Tasks or update to existing Technical Tasks. |
| Problem | How can the Development Team be enabled to realize a set of functionality instead of just realizing the Sprint Backlog Items? |
| Forces | too little/too much sticking to a given plan too little/too much context information |
| Solution | Agree on a Sprint Goal to give the Development Team’s work meaning. By involving the Development Team in that part of the planning process of the Product Owner, which drives the project towards the project’s goal, the Development Team can take over part of the responsibility for the deliverables. The Sprint Goal serves as the agreement between Development Team and Product Owner about the minimal functionality, which should be realized within a Sprint. If the Development Team finds out that it cannot reach the Sprint Goal, it can negotiate a change in the Sprint with the Product Owner to remove Sprint Backlog Items and still reach the goal. If the Sprint Goal cannot be saved, the Product Owner can stop the Sprint and start a new one immediately. |
| Resulting Context | The Development Team has guidance to enable it in changing the Sprint Backlog Items with the Product Owner as needed and the Product Owner has a base plan, based on which he can stop a Sprint. |
Dieser Artikel wurde von Andreas Heilwagen am 10.05.2011 um 10:07 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.
