Throughout iteration planning, the team elaborates the acceptance criteria for each story and estimates the effort to complete each one.
The Product Owner defines the ‘what’ the team defines ‘how’ and ‘how much’. During iteration planning, the Agile team discusses implementation options, technical issues, Nonfunctional Requirements (NFRs), and dependencies, then plans the iteration.
Typically, the Product Owner starts the event by reviewing the proposed iteration goals and the higher-priority stories in the team backlog. Prior to iteration planning, the Product Owner (PO) will have prepared some preliminary iteration goals, based on the team’s progress in the Program Increment (PI) so far. For more information on the definition of done, please see the ‘Scaled Definition of Done’ paragraph in the Built-in-Quality article.
Feedback from the prior iteration, including any stories that were not successfully completed (e.g., did not meet the ‘definition of done’) in that iteration. Additional stories that have arisen from a local context, including items such as defects and Refactors, as well as new stories that have come about since the planning session to support Feature delivery. The team’s PI plan, which consists of stories that were identified during PI planning and provisionally assigned to iterations. The Team and Program PI Objectives, created during PI planning. (They have usually held a backlog refinement event during the previous iteration.) There are a number of inputs to the iteration planning event: Teams approach iteration planning with a pre-elaborated Team Backlog. In SAFe, iteration planning is a refinement of the level of detail, and an adjustment of, the initial iteration plans created during PI planning. In return, management does not interfere or adjust the scope of the iteration, allowing the team to stay focused. At the end of planning, the teams commit to the goals of the iteration and adjust stories as necessary to achieve the larger purpose. The iteration backlog and goals are based on the team’s capacity and allow for consideration of each story’s complexity, size, and dependencies on other stories and other teams. Each Agile Team agrees on a set of stories for the upcoming iteration (the iteration backlog) and summarizes those stories into a set of iteration goals. The purpose of iteration planning is to organize the work and define a realistic scope for the iteration. A commitment by the team to the work needed to achieve the goals. A statement of Iteration goals, typically a sentence or two for each one, stating the business objectives of the iteration. The iteration backlog, consisting of the stories committed to for the iteration, with clearly defined acceptance criteria. 
That, and the natural course of changing fact patterns, provides the broader context for iteration planning. In addition, the teams have feedback-not only from their prior iterations but also from the System Demo and other teams they are working with. The team’s backlog has been seeded and partially planned during Program Increment (PI) Planning. Teams plan by selecting Stories from the Team backlog and committing to execute a set of them in the upcoming Iteration. The team summarizes the work as a set of committed Iteration Goals. Iteration Planning is an event where all team members determine how much of the Team Backlog they can commit to delivering during an upcoming Iteration. Stay committed to your decisions, but stay flexible in your approach.
0 kommentar(er)
