This artifact captures the key milestones of an iteration, showing start and end dates, intermediate milestones, synchronization points with other teams, demos, and so on. This artifact is also used to capture issues that need to be solved during the iteration.

You should list a few objectives for the iteration, which will help guide you throughout the iteration. Also, assess at the end if those objectives have been achieved.

The task assignments for an iteration are a subset of all tasks on the Artifact: Work Items List. Therefore, the iteration plan ideally references those work items.

The evaluation criteria and iteration assessment information are captured in this artifact, so that you can communicate results and actions from assessments.

Work items assigned to an iteration do not necessarily have the same priority. When selecting work items from the Work Items List, the iteration plan may end up having work items with different priorities (for example, you assign the remaining high priority work items, plus a few mid-priority ones from the Work Items List). Once work items have been assigned to the iteration, the team ensures that they can complete all work, regardless of original work item priorities. Deciding what to develop first on an iteration will vary across projects and iterations.