| Context | An estimated Product Backlog is available. |
| Problem | The customers wants to know when the next release is available and what features it will contain. Although the Product Backlog gives an overview of what will be implemented next, not all work is already broken down into chunks of work which can be realized in a Sprint. Furthermore, estimates for future work beyong the actual and the next Sprints are not precise. |
| Forces | too little/too much planning too little/too much commitment on constraints |
| Solution | Create a release plan and commit on a release date range Take your Product Backlog and assign the most important items to Sprints. Decide when a Sprint result will be released to the customer and communicate the important features and a planned release date including the information, that the release date may be a bit earlier or later due to the priorization process of Scrum. |
| Resulting Context | The customer has an expectation regarding the next release and its features. |
Dieser Artikel wurde von Andreas Heilwagen am 25.05.2011 um 08:57 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.
