| brainstorming | can help resolve conflicts over requirements |  |
| has definition The process of obtaining ideas, opinions, and answers to a question in a group environment in which all members of the group are given the opportunity to contribute | |
has advantages - in a group session people are energized and tend to spontaneously invent many good ideas, stimulated by what others have said
- introverted or timid people can have their say effectively since anonymity can be assured
| |
has procedure - Call a meeting with representation from all stakeholders
- Appoint an experienced moderator
- Arrange the attendees around the periphery of a table and give them plenty of paper to work with
- Decide on a trigger question
- Ask each participant to follow these instructions:
- Think of an answer to the trigger question
- Write the answer down in one or two lines on a sheet of paper, one idea per sheet
- Pass the paper to the neighbour on your left to stimulate their thoughts
- Look at the answers passed from your neighbour to the right and pass these on to your left as well. Use the ideas you have read to stimulate your own ideas
- Continue step 5 until ideas stop flowing or a fixed time (5-15 minutes) passes
- Ask everybody to read out one of the ideas on the sheets that happens to be in front of them. The moderator writes the each idea on a flip chart
- Take a series of votes to prioritize the ideas
| |
| has purpose to gather information from a group of people | |
| is a subtopic of 4.6 - Some Techniques for Gathering and Analyzing Requirements | |
| is related to Joint Application Development | |
| is a kind of requirements gathering | |
| should be done with five to 20 people | |
| uses a moderator (or facilitator) to lead the session | |
| requirements gathering | is part of requirements and specification | |
| process | see also process^2 | |
Object Oriented Software Engineering View all facts Glossary Help
