Definition of Terms:

• Assumptions:  That which is expected as a given for the project.  It is crucial that all assumptions be stated.
• Requirements: Functions that the software must be able to perform.
• Issues: Questions that stimulate debate or that require more information in order to answer.

Roles:
Facilitator - Starts the conversation among the participants and keeps it going. Provokes participants if needed.  Clarifies participants statements.  Assists the scribe in articulating Assumptions, Requirements, and Issues that are implicit in the conversation.  Helps moderate the flow of the conversation so the scribe has time to record items.

Scribe - Listens to the conversation and records comments into three categories (Assumptions, Requirements, Issues).  Checks with participants and/or facilitator that the ideas have been accurately recorded.

Participants - All stakeholders who use their imaginations to think up what would be really cool to be able to do.

Process:

• Facilitator introduces participants, frames the discussion, and explains how the conversation will be structured.
• Facilitator begins discussion by asking questions such as "What should this application be able to do?","What will a user do with this application?","What tasks to you imagine a user performing with this software?","What problem does this software solve?"
• The scribe and facilitator listen to the discussion and  pull out Assumptions, Requirements, and Issues and record them in separate places on a whiteboard, flip chart, etc.
• The facilitator or scribe ask questions to clarify statements made by participants.
• The session ends when the participants feel the problem requirements have been thoroughly understood.
• Consider ranking or prioritizing the requirements in order of importance to the customer, and in order of technical difficulty.

Success Tips:
Don't worry about getting every statement in the right category.  Focus on capturing all the information, and it can be categorized later.

Keep the conversation going by asking questions that prompt the participants to a full exploration of the desired system.

Issues don't have to be resolved during the discussion.  It's often best to set them aside after some initial discussion and assign each Isssue to one person for subsequent research or investigation.
 
Listening is key.  Try these good listening skills.