Written by Reedy Feggins, IBM
Work items are the fundamental mechanism in Rational Team Concert (RTC) used to coordinate, and track development tasks. RTC provides several out-of-the-box work items types including Epic, Story, Task and Defect. Each work item has its own workflow and associated set of attributes used to govern progress status, reporting and collaboration. Work items are the hub for linkage between many Rational Team Concert artifacts (e.g. other work items, builds, work items, and change sets), as well as providing support for integration with other products.
While RTC allows teams to link work items in any manner they choose, to keep it simple in when the customer is using the SCRUM Process Template, several of my customer implementation, I have recommended the following work item hierarchy: Epic story->Story -> Task/defect, see figure below.
User stories are a good approach to capturing customer requirements without having to create formalized requirement documents or incurring the extra effort to maintaining them. The intention is to speed up the requirement definition process, respond faster to changing requirements and communicate requirements in the language of the customer using scenarios that can be easily validated.
By default the RTC Scrum process template, Epics Stories are defined as top-level-item while Tasks are not. Each Story can be broken down into smaller tasks but it is not required. In addition we recommend that the RTC process template be updated to make the Defect a top-level-item.
Finally, RTC allows team to use the Work Item customization to create new work item types or modify existing ones in order to support the development process that your team follows. For additional information see Work item tracking on Jazz.net.
 APA: Work item tracking – Rational Team Concert – Projects – Jazz … (n.d.). Retrieved 02/20/2011 from http://jazz.net/projects/rational-team-concert/features/wi