1 Brainstorming CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 16, 2004.

Slides:



Advertisements
Similar presentations
AIP-2 Kickoff Workshop [Your Topic] Session Overview [Session co-lead names] GEOSS AIP-2 Kickoff September 2008.
Advertisements

Facilitating Effective Meetings
Policy development workshop The role and characteristics of appropriate supportive policy within Bandwidth Management and Optimisation (BMO)
Application of Nominal Group Technique: Benefits of Public Health Accreditation Patricia G. Porter, RN, MPH, CHES QI Toolbox.
An Introduction to Working Together
Why E-Moderate? An Overview of Some Key Benefits Amy Henderson - Module 3 (2) Team.
Brainstorming for Women of Power Leaders 1 A Philosophy For Business Success Richard Stewart/Anthony Butler.
Designing Influential Evaluations Session 1 Introduction Uganda Evaluation Week - Pre-Conference Workshop 19 th and 20 th May 2014.
Understanding User and Stakeholder Needs
Meetings, Meetings, Meetings Can they be better? YES! Kathleen Paulo, MSW 1.
1 Brainstorming and Storyboarding Sriram Mohan/Steve Chenoweth RHIT Chapters 12 & 13, Requirements Text.
1 Quality CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 25, 2004.
Ambiguity and Specificity CSSE 371, Software Requirements and Specification Steve Chenoweth, Rose-Hulman Institute October 19, 2004 In the book – This.
1 Use Cases 1 CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 17, 2004.
1 Interviewing CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 13, 2004.
1 Problem Analysis CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 9, 2004.
Introduction CS 414, Software Engineering I Mark Ardis and Don Bagert Rose-Hulman Institute December 2, 2002.
Introduction to Requirements (Chapters 1-3 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman Institute.
1 Team Skill 4 - Team Skill 5 - Scope Refining the Systems Definition (Chapters of the requirements text) CSSE 371 Software Requirements and Specification.
Slide 1 Requirements Wrap-up (Chapter 31 of requirements text) and Interaction Design: Introduction (Chapters 1 of Interaction Design text) CSSE 371 Software.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.
1 Scope CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute October 11, 2004.
1 PrototypingPrototyping CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 28, 2004.
Diversity of Interaction in a Quality Assurance Course Mark Ardis, Rose-Hulman Institute Cheryl Dugas, Indiana State University FIE 2005.
1 Team Skill 1 - Analyzing the Problem (Chapters 5-7 of the requirements text) CSSE 371, Software Requirements and Specification Don Bagert, Rose-Hulman.
Brainstorming and Idea Reduction
Chapter 11 Requirements Workshops
Team Skill 2 Understanding Stakeholders Needs
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
PDMU Team 2010/2011 Daphne Wilson.
Requirements Workshops
Facilitator Training Program. Day One Agenda – Day One Welcome Getting Started Activity Course Objectives Overview of Facilitation Skills Facilitation.
Creative Training Ideas Presented by Your Name. Agenda Overview Introduce the Team Brainstorming Objectives Rules for Brainstorming Brainstorming Activities.
Effective Meetings Leadership 12. Meetings While meetings are wonderful tools for generating ideas, expanding on thoughts and managing group activities,
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.
Requirements Elicitation Techniques. Interviewing and questionnaires.
Karen A. Blase, PhD & Allison Metz, PhD Frank Porter Graham Child Development Institute University of North Carolina – Chapel Hill Terms of Reference:
A professional learning group; how to stimulate learners’ engagement in problem solving Alia Sheety & Frida Rundell 531 Main Street, Bethlehem Pa
Basic Impact Evaluation Course Poverty Analysis Initiative (C102) Poverty Analysis Initiative (C102) World Bank Institute Attacking Poverty Program.
Team Skill 2 Understanding User and Stakeholder Needs Requirements Workshop (11)
Workforce Planning Model Workshop December 2007 WELCOME.
Project Management Workshop Overview By Tarek Lahdhiri Region 4 PACE Chair IEEE Region 4 Meeting January 30/31, 2004.
O Gets the team off to a quick start o Make sure everyone understands the task o Makes sure that everyone's voice is heard o Organises and motivates their.
Group Communication. Groups A. Names 1.Committee – specialized task 2.Team – power to make decisions 3.Advocacy – formed to support & defend causes of.
Lecture 10 More Innovation SE3821 Software Requirements and Specification Dr. Rob Hasker (based on slides by Dr. Brad Dennis)
October 1, 2014 Welcome to ENG 1450 Writing and Reading for Problem Solving ***Please keep homework & report at your desk.***
1 Brainstorming and Storyboarding Sriram Mohan. 2 Outline  Background Barriers to Elicitation  Techniques Brainstorming Storyboarding.
Regional Workforce Development Coalition Strategic Planning Process Planning Session I April 8, 2014.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) Sriram Mohan.
Fast Food Debate Learning Target: I can work collaboratively with my group. I can establish norms with the opposition for debate. I can use factual research.
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.
What Leaders Do & Introduction to Personal Case Discussions BMA 533 September, 2005.
World Literature and Composition. Warmup Work for 3 minutes on the top portion of the “Many Voices, Many Selves” worksheet. Spend 2 minutes sharing with.
SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 1 Chapter 12: Brainstorming and Idea Reduction.
Fundamentals of Software Development 1Slide 1 Team management What can you do to help your team work effectively?What can you do to help your team work.
Team management What can you do to help your team work effectively?
STUDENT VOTE BEST PRACTICES
September 17, 2009 Workshop Agenda
VP, Institutional Services
QUALITY IMPROVEMENT FINAL QUARTERLY COLLABORATIVE WORKSHOP
Team-building Workshop: The Standard Agenda
Chapter 19 Speaking in and as a Group
Chapter 11 Requirements Workshops
Affinity Diagram.
Group Communication Notes
Facilitating a Committee
Agenda – week 10 6:00 – 6:05 Questions, announcements 6:05 – 6:30
Team-building Workshop: The Standard Agenda
Interviewing Sriram Mohan.
Running a workshop: the role of the facilitator
Presentation transcript:

1 Brainstorming CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 16, 2004

2 Benefits of Requirements Workshop All stakeholders get their say May expose political issues Helps form effective team

3 Facilitator Establish proper tone Introduce goals and agenda Keep team on track Facilitate decision making Make sure all voices are heard

4 Agenda Introduction [.5 hr] Context [1.5 hr] Brainstorming [2 hr] Lunch [1 hr] Brainstorming [1 hr] Feature definition [1 hr] Idea reduction [1 hr] Wrap-up [1 hr]

5 Brainstorming Benefits 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

6 Method Write down ideas on stickies Read ideas out loud No criticizing!

7 Idea Reduction Group ideas Vote Pick best ideas