Representation Options |
The recommended representation for the work items list is to capture it as a separate artifact,
represented by a spreadsheet or database table. See Example: Product Backlog.
Alternatively, the work items list may be captured in tools such as project management, requirements management, or
change request. In fact, the work items list may be spread over several tools, as you may choose to keep
different types of work items in different repositories to take advantage of features in those tools. For example,
you could use a requirements composition or management tool to track information about requirements, and use another
tool to capture defects. Work items may start in one representation (such as in a spreadsheet) and move to more
sophisticated tools over time, as the number of work items and the metrics you wish to gather grows more sophisticated.
As part of the Iteration Plan
The Iteration Plan (Project Level) typically references work items that are assigned to that iteration.
If the team is capturing the iteration plan on a whiteboard, for example, the team may choose to reference high-level
work items in the Work Items List that are assigned to the iteration, and maintain low-level child work items used to
track day-to-day work only in an iteration plan.
|