To plan an iteration, determine the right balance of scenarios, quality of service requirements, and bug allotments for the upcoming iteration. The amount of work that can be completed in an iteration is limited. The scenarios and quality of service requirements with the biggest business value are prioritized for inclusion in the current iteration. An initial iteration plan is created using the scenario entries and quality of service requirements which have rough order of magnitude estimates. Once the scenario entries are part of the iteration plan, the corresponding scenarios are written by the business analyst. Developers and testers then divide the scenarios into tasks. These new tasks are chosen by the developers and more detailed costs are provided. The new detailed estimates are used to load balance the tasks assigned to developers. The iteration planning meeting brings together the appropriate business analysts, project managers, and developers to finalize the iteration plan.