You can browse the jazzdev repository (available on jazz.net) for
examples (currently, there are 119 retrospective work items in jazzdev).

Commonly, the description of the work item will be initialized with the
areas of feedback the component lead is particularly interested in, and
individuals will add comments with their particular feedback. The
project lead will often then update the description to summarize that
feedback. If a project lead wants to make sure everyone on the team
contributes to the retrospective, they can create "approvals" for each
team member.

Cheers,
Geoff



John T. Kohl wrote:

In previous releases, I've used a new tab on an iteration plan to hold
wiki-markup formatted retrospective notes.

The Scrum process in RTC 2.0 has a "retrospective" work item type with a
very simple work flow (open, in progress, closed).

I haven't found any substantive documentation for this type on jazz.net
(at least google search can't find anything substantive).

Anybody here have suggestions/examples of use of this type?