Iteration plan

Rational Team Concert™ projects are organized into a series of fixed-length development periods called iterations. Each timeline has its own set of iterations. An Iteration plan displays the goals to be achieved in an iteration. You can create an iteration plan and assign work items that are to be completed in an iteration.
Note: If you follow the Scrum process template, an Iteration plan is called a Sprint Backlog.
By default, an Iteration plan groups work items based on the following plan modes:

Example

Planning a Sprint

You can use the Plan Editor to manage sprint backlogs. As with a product backlog, the editor assists you with stack ranking your sprint backlog. In addition, the Plan Editor provides a view to display the work breakdown structure of all work items, grouped by the owners. Drag and drop or specific keyboard actions are used to manipulate the work breakdown structure or reassigning the task to do load balancing. Key work item attributes, like the estimate of a task, can be changed in place and the changes are immediately reflected in the corresponding progress and load bars.

In the View As section select Developer's Taskboard. The view renders all work items as cards on a board, arranging them in columns representing three states: To Do, In Progress, and Done. This allows for a quick overview of your work. To mark a work item as complete, simply drag it from To Do or In Progress column to the Done column.


Feedback