Iteration plan

The iteration plan plans out a specific iteration in more detail, so that the planning horizon is a single iteration. This is typically 1-4 weeks in duration. This is the last chance to adjust the expectations of the iteration before work begins.

Purpose

The purpose of the iteration plan is to ensure that the work allocated to the iteration is achievable, decompose the larger-scale work items (for example, use cases and technical work items) into smaller work items, and plan for completion of the iteration.

Inputs and preconditions

Preconditions include the release plan and the initial iteration backlog.

Outputs and post conditions

Post conditions include the complete work items, generated engineering work products, identified defects, and technical work items (pushed into the product backlog), and uncompleted work items (also pushed back onto the product backlog).

How to do it…

Use cases in the iteration backlog, which may take an...