Scenarios in Practice

Scenarios have been discussed in the HCI literature since at least 1992. Since then, they have
come into the mainstream: There are books and tutorials on the topic; every published UCD
method incorporates them in some form. The current challenge facing the scenario community is
making scenario usage more effective and efficient in industry projects. This workshop fills that
need by focusing on "scenarios in practice" as opposed to "the theory of scenarios" or "anything
about scenarios".

Although we use the term "scenarios", the workshop welcomed various communities of practice
including personas, stories, and use cases. What was common among the participants is a usercentered
perspective. The word "scenario" in this report refers to any of these communities of
practice.

The scope of this workshop includes the overlapping concerns of: deploying a scenario
methodology into a project environment, integrating scenarios with other UCD methods, craft and
quality in writing scenarios, and tailoring scenarios to various project contexts. The workshop was
divided into four segments, which loosely follow the phases of writing and using scenarios:
Identifying where scenarios come from, defining scenario topics, writing scenario content, and
using scenarios that have been written.

This report summarizes the key points from each segment of the workshop. To stimulate
discussion, participants completed several exercises. The exercise material is summarized in the
appendix.

By: Paul McInerney, Michael J. Muller

Published in: RC22931 in 2003

LIMITED DISTRIBUTION NOTICE:

This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.

RC22931.pdf

Questions about this service can be mailed to reports@us.ibm.com .