SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 1 Chapter 12: Brainstorming and Idea Reduction.

Slides:



Advertisements
Similar presentations
BRAINSTORMING BURÇİN AKI WHAT IS BRAINSTORMING? Brainstorming is a group activity technique.It is designed to generate lots of ideas for solution.
Advertisements

Idea Generation And Synthesis for Writing Facilitation and Interaction IDENTIFY EVALUATEE ANALYZE ADOPT.
Account Planning The purpose of these slides is to describe the Account Planning Process, the methodology, and the workload involved in running an account.
Affinity Diagrams.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text.
1 Brainstorming CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 16, 2004.
Decision Methodologies
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.
Problem Solving and Decision Making A situation that exists when objectives are not being met. Problem Solving The process of taking corrective.
PowerPoint Presentation by Charlie Cook Creative Problem Solving and Decision Making Chapter 4 Copyright © 2003 South-Western/Thomson Learning. All rights.
Brainstorming and Idea Reduction
Chapter 11 Requirements Workshops
Facilitation Richard Fisher. 10/9/2000Facilitation - Richard Fisher2 Facilitated Sessions A structured meeting technique designed to gather information.
Customer Focus Module Preview
Team Skill 2 Understanding Stakeholders Needs
Lean Supply Chain Action Learning Program September 2007.
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
Brainstorming. Brainstorming Sequence One team member should review the topic of the brainstorm using "why", "how", or "what" questions. Example: The.
Leaders Manage Meetings
Reflective practice Session 4 – Working together.
WorkOut Method A3 for Facilitators What is a WorkOut? A methodology that helps teams identify opportunities to improve the way work gets done. Why are.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 7 Determining.
9 Closing the Project Teaching Strategies
Quality Function Deployment
Brainstorming 1. “The hardest single part of building a software system is deciding precisely what to build. No other part of the conceptual work is as.
Making the Most of Brainstorming Presenter’s Name Copyright © Texas Education Agency All rights reserved.
 The model consists of 6 steps: Step 1: Define the problem or opportunity. Step 2: Set objectives & criteria. Step 3: Generate alternatives. Step 4:
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Requirements Elicitation Techniques. Interviewing and questionnaires.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
IW:LEARN TDA/SAP Training Course
Lessons Learned Workshop
Encouraging Creativity & Innovation in a Team Professional Year Program - Unit 5: Workplace media and communication channels.
Brainstorming! Click left mouse button or press space bar to advance presentation. Click right mouse button to go back. Press ‘Esc’ key to exit.
Brainstorming! Click left mouse button or press space bar to advance presentation. Click right mouse button to go back. Press ‘Esc’ key to exit.
Brainstorming and Meetings
Strategic Planning: Developing Strategic Initiatives 1.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
Creativity and the Decision Making Process Business Management Chapter 8.2.
Chapter 6 Determining System Requirements. 2 2 What are Requirements? “Requirements are … a specification of what should be implemented. They are descriptions.
Chapter 05 Decision Making, Learning, Creativity, and Entrepreneurship McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights.
The Team Meeting Process Author: VCU T/TAC Clipart found at:
Database Analysis and the DreamHome Case Study
© 2007 The McGraw-Hill Companies, Inc. All rights reserved. Serving as Designated Leader © 2007 The McGraw-Hill Companies, Inc. All rights reserved. C.
User Interface Design & Usability for the Web Card Sorting You should now have a basic idea as to content requirements, functional requirements and user.
© ABSL Power Solutions 2007 © STM Quality Limited STM Quality Limited Brainstorming TOTAL QUALITY MANAGEMENT Brainstorming.
Quality Tools. Decision Tree When to use it Use it when making important or complex decisions, to identify the course of action that will give the best.
Brainstorming. To invent new way of doing things or when much is unknown – When there are few or too many ideas – Early on in a project particularly when:
Overcoming Barriers for your Change Initiatives.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Lecture 10 More Innovation SE3821 Software Requirements and Specification Dr. Rob Hasker (based on slides by Dr. Brad Dennis)
1 Brainstorming and Storyboarding Sriram Mohan. 2 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding.
Strategic Planning Building Connections: Community Leadership Program Improving Lives. Improving Texas.
Small Group Work as Teaching Strategy By P. Anand Ganesh Resource person & PGT ( CS) K V 2 Golconda, Hyderabad.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) Sriram Mohan.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Requirement Engineering
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
An Agile Requirements Approach 1. Step 1: Get Organized  Meet with your team and agree on the basic software processes you will employ.  Decide how.
Nominal Group Process (NGP) A well researched technique (Delbecq et al., 1986) that is effective in facilitating a group to come to the best combined judgements.
A focus group is actually gathering of people who are customers or users representatives for a product to gain its feedback. The feedback can be collected.
Group 9: Matilda Akkola, Reetta Arokoski, Lauri Kokkila, Miikka Laitila CROWDSOURCING: HOW TO BENEFIT FROM (TOO) MANY GREAT IDEAS? “The article gives recommendations.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
Interviewing S.Vidya,AP/CSE.
The Check List Method and Reverse Brainstorming
Chapter 2 The Process of Design.
Chapter 11 Requirements Workshops
Solving Workplace Problems
Solving Problems in Groups
Presentation transcript:

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 1 Chapter 12: Brainstorming and Idea Reduction

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 2 Objectives To introduce brainstorming and idea reduction technique.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 3 Brainstorming l Brainstorming is a group technique for generating new, useful ideas and promoting creative thinking. l It can be used to help elicit new ideas and features for the application define what project or problem to work on, to diagnose problems, remediate a project by coming up with possible solutions and to identify possible resistance to proposed solutions

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 4 Roles l There are three roles for participants in a brainstorming session: Leader -This person needs to be a good listener, Scribe -This person needs to write down EVERY idea - clearly and where everyone in the group can see them and team member - participants

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 5 Brainstorming l Typically, a portion of the workshop is devoted to brainstorming new ideas and features for the application. l Brainstorming elicitation technique has a number of benefits. It encourages participation by all parties present. It allows participants to "piggyback" on one another's ideas. It has high bandwidth. Many ideas can be generated in a short period of time. The results typically indicate a number of possible solutions to whatever problem is posed. It encourages out-of-the-box thinking, that is, thinking unlimited by normal constraints.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 6 Phases of Brainstorming l Brainstorming has two phases: idea generation and idea reduction. l Idea generation The primary goal during idea generation is to set down as many ideas as possible, focusing on breadth of ideas, not necessarily depth. l Idea reduction The primary goal during idea reduction is to analyze all the ideas generated. Idea reduction includes pruning, organizing, ranking, expanding, grouping, refining, and so on.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 7 Rules for Brainstorming l First, all the significant stakeholders gather in one room, and supplies are distributed. l Then the facilitator explains the rules for brainstorming.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 8 Objective of Brainstorming l The facilitator also explains the objective of the process. The following questions are a few ways to state the objective. What features would you like to see in the product? What services should the product provide? What opportunities are we missing in the product or the market? After stating the objective of the process, the facilitator asks participants to share their ideas aloud and to write them down, one per sheet

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 9 Idea Generation l When a person comes up with an idea, he or she writes it down on the supplied materials. This is important for the following reasons: To make sure the idea is captured in that person's own words To make sure ideas are not lost To enable posting of ideas for later piggybacking To prevent delays in the creative process that could be caused by a single scribe trying to capture all ideas on a flip chart or whiteboard in front of the room

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 10 Idea Generation (Cont’d) l As ideas are generated, the facilitator collects them and posts them on a wall in the meeting room. l Again, no criticism of ideas can be tolerated. It is inappropriate to say, "That's a stupid idea," or even, "We already have that idea on the wall." The sole purpose is to generate ideas. The process tends to have a natural end; at some point, the stakeholders will simply run out of ideas.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 11 Idea Reduction 1.Pruning Ideas The first step is to "prune" those ideas that are not worthy of further investment by the group. The facilitator asks the participants whether each idea is worthy of further consideration and then removes an invalid idea The presence of ideas that can be easily pruned is an indicator of a quality process.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 12 Idea Reduction (Cont’d) 2.Grouping Ideas It may be helpful during this process to start grouping similar ideas Name the groups of related ideas. For example, New features Performance issues Enhancements to current features User interface and ease-of-use issues

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 13 Idea Reduction (Cont’d) 3.Defining Features In this process, the facilitator walks through each idea that has not been pruned and asks the submitter to provide a one- sentence description. This gives the contributor the opportunity to further describe the feature and helps ensure that the participants have a common understanding of the feature. Examples:

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 14 Idea Reduction (Cont’d) 4.Prioritizing Ideas Cumulative Voting: The Hundred-Dollar Test "Critical, Important, Useful" Categorization Critical means indispensable, suggesting that a stakeholder would not be able to use a system without this feature. Important means that there could be a significant loss of customer utility, perhaps even market share or revenue, or new customer segments served without the feature. Useful means nice to have. Each stakeholder is given only one-third of the votes from each category.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 15 Web-Based Brainstorming l Sometimes live brainstorming is not possible. l In these situations, an alternative is to use the Internet or an intranet to facilitate the brainstorming process in a collaborative environment l An advantage of this technique is its persistence Ideas and comments can be circulated over a long period of time, with full recording of all threads for each idea.

SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 16 Key Points l Brainstorming involves both idea generation and idea reduction. l The most creative, innovative ideas often result from combining multiple, seemingly unrelated ideas. l Various voting techniques may be used to prioritize the ideas created. l Although live brainstorming is preferred, Web-based brainstorming may be a viable alternative in some situations.