Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.

Slides:



Advertisements
Similar presentations
Change Proposal: When to Use It Use this format when you are suggesting a change. If your audience will consider it an unpleasant change, you may want.
Advertisements

Whiteboard Content Sharing Audio Video PollsRecordingMeet Now Skype Integration MS Lync 2013 Tools & Tips for facilitators… Limitations Alternatives One.
Problem Solving.
Lesson 15: Coaching Skills
Assessment for Learning Tools and Activities. Links to Tools and Activities Comment-only marking Exemplar Work Student Marking Traffic Lights Self-assessment.
Compiled from sources found on the internet by: Lara Arch
BSBIMN501A QUEENSLAND INTERNATIONAL BUSINESS ACADEMY.
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.
PPA 691 – Policy Analysis Brainstorming and Assumptional Analysis Procedures.
The Information School of the University of Washington Interviews: Analyzing interviews/practicing interviewing.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.
“Muddy point” one-minute papers
Oct. 30, 2003CS WPI1 CS 509 Design of Software Systems Lecture #9 Thursday, Oct. 30, 2003.
Brainstorming and Idea Reduction
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 1. Interviews 2. Workshops 3. Brainstorming.
Functional Requirements – Use Cases Steve Chenoweth & Chandan Rupakheti (Chapters 14, 21 – Requirements Text)  Quiz question 9 relates to this, when you’ve.
Socratic Seminar Ms. Melvin.
Problem solving in project management
Brainstorming. Brainstorming Sequence One team member should review the topic of the brainstorm using "why", "how", or "what" questions. Example: The.
Organizing Requirements & Managing Scope (Chapters of the requirements text ) Steve Chenoweth & Chandan Rupakheti RHIT Which brings up Question 1,
Team Skill 1 - Analyzing the Problem Steve Chenoweth & Sriram Mohan Pages 43 – 52 in Requirements Text.
1 Conducting software project assessments Kan, Ch 16 Steve Chenoweth, RHIT.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Elizabeth Jean Bingham Central Elementary
to Effective Conflict Resolution
Find out more about your family.  We are all going to learn a little bit more about ourselves and our heritage by interviewing an older family member.
Personas & Interviewing Steve Chenoweth & Chandan Rupakheti RHIT Chapter 10 - Requirements Text Links to Personas ref’s on the web Quiz 3a, Question 10.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Have you implemented “Number Talks” in your classroom? What are the pros? What are the cons? Any suggestions?????
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.
Requirements Engineering Requirements Elicitation Process Lecture-9.
JFK-103B1W9 and JFK-103B3W9 This program is going to be used to learn about:  Decision Making Skills  Communication Skills  Team Building Skills and.
How to start Milestone 1 CSSE 371 Project Info There are only 8 easy steps…
A Solution Oriented Approach In Educational Settings The aim of this series of training sessions is to give an introduction to the principles of solution.
Usability testing: A reality check for Plain Talk A brief overview October 7, 2008 Dana Howard Botka Manager, Customer Communications, L&I Plain Talk Coordinator,
Applied Software Project Management
Collaboration for Student Empowerment
© ABSL Power Solutions 2007 © STM Quality Limited STM Quality Limited Brainstorming TOTAL QUALITY MANAGEMENT Brainstorming.
P UTTING T HE F IVE P RACTICES OF E XEMPLARY L EADERSHIP I NTO P RACTICE.
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:
Team Skill 2 Understanding User and Stakeholder Needs The Challenge of Requirements Elicitation (8)
Warm-up Ideas Warm-ups help your learners put aside their daily distractions and focus on English. If they haven't used English all day, they may take.
Finding the balance between games, learning and communicativity. Presented by Martin McCloud
1 Brainstorming and Storyboarding Sriram Mohan. 2 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding.
Storyboarding Steve Chenoweth & Chandan Rupakheti RHIT Chapters 13, Requirements Text and storyboarding web article.
Monday September 14th, 2015 Planner: – HW: Safety rules poster due Wed. 9/16 – Safety Quiz tomorrow - based on rules You Need: – Today: Daily 5 To Do:
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.
Problem Solving Skills
/0604 © Business & Legal Reports, Inc. BLR’s Training Presentations Effective Decision-Making Strategies.
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
BES-t Practices Training Phase 3 Counseling – Behavior Modification.
THE “COLLEGES I AM THINKING ABOUT” LIST IN YOUR FAMILY CONNECTIONS ACCOUNT.
Conducting Effective Meetings. Have an Agenda Outline prior to meeting what points will be covered. Write it out, and distribute it to participants ahead.
INFO 638Lecture #91 Software Project Management Conclude Adaptive Project Framework INFO 638 Glenn Booker.
SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 1 Chapter 12: Brainstorming and Idea Reduction.
Chapter 5 Trawling For Requirements. Determining What the Product Should Be without understanding the work that it is to become a part of Many projects.
Laboratorio di lingua inglese 3
PROBLEM SOLVING June 2010 CANADIAN COAST GUARD AUXILIARY - PACIFIC.
Interviewing S.Vidya,AP/CSE.
Laboratorio di lingua inglese 3
Laboratorio di lingua inglese 3
Designing a Research Package
Key Elements of Class Meetings
Laboratorio di lingua inglese V
Interviewing Sriram Mohan.
ELLs in Texas: What Teachers Need to Know
Presentation transcript:

Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating lots of ideas, usually from lots of people.

Outline  Background Barriers to Elicitation  Techniques Brainstorming – Monday & Tuesday  Ch 12 in Requirements book Storyboarding – also Tuesday  Ch 13 in Requirements book

Three Common Barriers  “Yes, But…” Syndrome Develop techniques to get rid of the “But” early.  Undiscovered Ruins Syndrome “the more you find, the more you know” --> find the right balance  User and Developer Syndrome Communication gap between the users.

Outline  Background Barriers to Elicitation  Techniques Brainstorming – this slide set and quiz Storyboarding – next slide set and quiz

When do you brainstorm?  Nobody already knows the answer, but they do have some starting ideas. Or,  Several people think they do, but they have different answers! Or,  You know you need to get different perspectives on an issue. Or,  Nobody has any idea, but you can assemble experts and people familiar with the problem, and maybe get started on an idea. Monday’s quiz – Q 1

What’s involved in the preparations?  You need to identify the “client” for the brainstorming, and arrange with them, ahead of time, to limit the scope of what you want to brainstorm about.  You need to talk with each of the other participants, and Find out what their “stake” is in solving this problem. Get them to consider ways they think might work, to solve the problem. Monday’s quiz – Q 2

How do you start the brainstorming session?  Describe what’s going to happen, the whole process, to the whole group.  The client describes a short version of the problem, in a couple minutes.  You, the facilitator, write it on the board. Try to capture all of it. So, ask them to repeat if you miss something. Monday’s quiz – Q 3

Here’s the whole process – The Phases of Brainstorming  Describe the problem clearly  Discover = Idea Generation New Ideas Idea Development  Decide = Idea Reduction Eliminating Combining Choosing Describe Discover Decide Monday’s quiz – Q 4 You are now here 

 Encourages participation by all  Allows participants to build on one another's ideas  High bandwidth: many ideas in short period of time  Encourages out-of-the-box thinking Benefits

Describe  Everyone has to agree on the problem to be brainstormed before you start. The traditional method of having the “client” just define this at the start – that’s a shortcut.  If you have shared client-ship - It helps if they all have time beforehand to think of ideas on their own.

Discover  This is brainstorming proper.  We’ll try one method today, then others tomorrow.

Discover - One Brainstorming Method  Write down ideas on post-it notes, put on wall  Read ideas out loud  Capture ideas in person’s own words  Generate as many ideas as possible  No criticizing!  Take turns being the facilitator

Discover - A Similar Method  Use an easel or whiteboard  Ask for ideas and write them down as they are said aloud  While facilitator writes down the “headline” for each idea, the person giving it can explain just a little more  Try to get more ideas related to ones you are hearing  Once again - no criticizing!

Discover - Idea Development  Find ideas that are “most intriguing” Usually they have some “issues” but also a lot to like  Pick one, and brainstorm ways to “push them toward acceptable”  Then do this to a couple more  Gives “ideas about these ideas” which could make them into winners

Decide - Idea Reduction  Prune ideas…, After the crazy and wild ones disappear  Give one-line description for each remaining idea  Combine ideas  Classify the ideas into groups Monday’s quiz – Q 5

Idea Reduction…  But there are situations, where not all ideas can be taken forward, in this case we have to choose the ideas that we take forward. How do we do this? See if any more can be combined Vote on the ideas (i.e. rank them) Prioritize the ideas Try to decide based on “acceptable risk” and “desired opportunities” so you don’t end up with just easy ones everyone already knew Try to leave with “as many as you can afford to consider further”  Put all remaining ideas on someone’s action list to develop

Web based brainstorming  Using the internet to facilitate the brainstorming in a collaborative way.  Is this useful? Why?  How do we do it?

Practice Brainstorming – We’ll Do This as Teams  Describe - Features, requirements, enhancements, user interfaces or anything that you would like to see on the degree planner project.  Discover - Idea Generation (14 minutes) Let’s generate ideas for this. (7 minutes) Find ones that are intriguing & find ways to support those (7 minutes)  Decide - Once we are done let’s practice Idea Reduction (10 Minutes) (Eliminate invalid ideas) – if you’re not very daring!  Else, try to think of ways to make them more acceptable Group those that should go together One line description of categories Decide - Voting & Prioritizing  Leave with action list