| Context | A Sprint Backlog (“Selected Backlog” before the Scrum Guide 2011) is available and the Development Team understands all business requirements in it. |
| Problem | What needs to be done to turn the Sprint Backlog Items into a done increment and how can it be managed? Besides the need for transforming business requirements into technical requirements by writing Technical Tasks where needed in order to realize Sprint Backlog Items, work needs to be broken down into manageable chunks which are estimated, so that they can be assigned, tracked and reported. |
| Forces | too little/too much technical planning too little/too large Technical Tasks too little/too much complexity |
| Solution | Break down the Selected Backlog into a Sprint Backlog. Discussing the draft design of the solution to realize the Sprint Backlog enables the Development Team to create Technical Tasks where needed. These tasks can be estimated and managed to drive the Sprint. Most Technical Tasks are discovered at the beginning of the Sprint, new Tasks are added during the Sprint by the Development Team as required. If the Development Team is not able to realize all Tasks, the open tasks are rated as incomplete and can be transferred to the next Sprint. |
| Resulting Context | The Development Team can manage the implementation of the Sprint Backlog by selecting tasks and reporting remaining work. |
Dieser Artikel wurde von Andreas Heilwagen am 28.04.2011 um 11:14 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.
