| Context | A Product Backlog is available and a Scrum Team has been formed. |
| Problem | What work should be done next by the Development Team to reach a given goal and how shall this work be done? |
| Forces | too little/too much technical planning too little/too much communication vs. written documents too little/too much organizational overhead |
| Solution | Conduct two Sprint Planning Meetings, one with business focus and one with technical focus. Let the Product Owner communicate prioritized Product Backlog Items (PBIs) to the Development Team to fill a Sprint in the first meeting. Ensure that the selection of the PBIs is coordinated with the Development Team and a Sprint Goal is agreed to define the purpose of the Sprint. Next conduct a Sprint Planning Meeting II to let the team come up with a rough design of the solution as well as a plan to implement the PBIs. The PBIs selected for realization in a Sprint have been named Selected Backlog inofficially, beginning with the Scrum Guide 2011 they are called Sprint Backlog, replacing the old meaning of the term. |
| Resulting Context | The Scrum Team is ready to implement the selected Product Backlog Items. |
Dieser Artikel wurde von Andreas Heilwagen am 27.04.2011 um 12:05 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.
