|
1. Identify sources for Product Backlog items
Backlog items may be documented in a variety of sources, such as a Product Vision, customer
surveys, or a requirements database. Importing from those sources into a single backlog makes them
easier to manage.
|
|
|
2. Import existing backlog items
It may be possible to automatically import some backlog items from existing sources.
|
If you have existing backlog items in a spreadsheet, you can import them into Rational Team Concert
using the Eclipse client. See Importing Work Items from a CSV File. An example CSV file is included
with the tutorials. The example can be used as a template for your own work items.
|
|
3. Add new items to the Product Backlog
Add new items to the backlog from existing sources, if they are to be considered for development.
Typically these will be Epics or Stories.
Break down Epics into Stories if the Epic will likely be delivered in more than one
release.
|
a. Open the Product Backlog. (In the web interface, click Plans > All
Plans. Then click Product Backlog.)
b. Click Add Work Item to add a work item. Typically this will be an Epic or
Story.
c. Populate the work item, filling in the Summary as a minimum. Project
Area will already be set to the your project and Planned For will
already be set to Backlog.
d. To break down an Epic into Stories, set View As to Work
Breakdown, then click to the left of the work item to be decomposed and click Create
Child Work Item.
You can also drag and drop a story onto an Epic in order to make it a child of that Epic.
|
