1) Read Only (Mashup)

In this scenario, read only access from two systems is necessary. In the Rally mashup with Quality Center, a read-only view of Rally stories is shown with a read-only view of the Quality Center defects related to each story. There is no need to update any items in either system in this scenario. This could also be described more simply as a read only view from one system.

2) Read/Write (IDE Plugin)

In this scenario, read/write access is necessary to update work items. For example, Rally stories, tasks, and defects are available to view/edit in the Eclipse IDE. In this scenario, meta data can be important to describe allowed values.

3) Translate (Connector)

In this scenario, read/write access to Rally stories and read/write access to another system are needed. One example is the Rally Connector for ClearQuest? where a test group might want to use CQ for defect management but the development group wants to copy those defects to Rally so they can schedule them into iterations, etc. An important aspect of this scenario is the ability to make mapping decisions between the two systems since some fields (like priority or severity) might not match between the two systems. The other interesting differentiation of this scenario is that the 'same' defect exists in both systems - very different than the first two scenarios.

-- MarkRinger - 29 Oct 2009