Personas & Interviewing Steve Chenoweth & Chandan Rupakheti RHIT Chapter 10 - Requirements Text Links to Personas ref’s on the web Quiz 3a, Question 10.

Slides:



Advertisements
Similar presentations
Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 1.Gain agreement on the problem definition. 2.Understand the root causes 3.Identify the.
Advertisements

Virtual University - Human Computer Interaction 1 © Imran Hussain | UMT Imran Hussain University of Management and Technology (UMT) Lecture 20 User Research.
Name of your startup: Your idea in max 160 characters: Contact: Website: City: Phase: idea concept MVP launched Team member 1 Name: Role: Team member 2.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
1 Interviewing CSSE 371 Software Requirements and Specification Mark Ardis, Rose-Hulman Institute September 13, 2004.
CAP 252 Lecture Topic: Requirement Analysis Class Exercise: Use Cases.
Topics: Interviewing Question Type Interviewing techniques
Feb. 6, 2001CSci Clark University1 CSci 250 Software Design & Development Lecture #7 Tuesday, Feb. 6, 2001.
Slide 1 Process, Requirements and Prototyping (Chapters 6-8 of Interaction Design text) CSSE 371 Software Requirements and Specification Don Bagert, Rose-Hulman.
Feb. 2, 2004CS WPI1 CS 509 Design of Software Systems Lecture #3 Monday, Feb. 2, 2004.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.
Oct. 2, 2003CS WPI1 CS 509 Design of Software Systems Lecture #5 Thursday, Oct. 2, 2003.
Administrivia Turn in ranking sheets, we’ll have group assignments to you as soon as possible Homeworks Programming Assignment 1 due next Tuesday Group.
FOCUS GROUPS & INTERVIEWS
Chapter Four Copyright © 2004 John Wiley & Sons, Inc. Secondary Data & Databases.
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
Purdue OWL Staff A workshop brought to you in cooperation with the Purdue Online Writing Lab Field Research: Conducting an Interview.
Crystal Reports Developer Advantage New, cost effective licensing option.
Chapter 33 Conducting Marketing Research. The Marketing Research Process 1. Define the Problem 2. Obtaining Data 3. Analyze Data 4. Rec. Solutions 5.
INFO101: Management Information Systems INFORMATION X.
This Lesson Introduction to the ADDIE model Needs Analysis
Basic Terms Research—the process of finding information relevant to a particular topic Source—any medium that provides information relevant to a particular.
Approaches to Investigating a System “Who knows what’s happening now?”
A Network Marketer’s Template for Creating a Target Audience Profile [name] [demographic] [goals] [and more]
CS 111 – Nov. 19 Enterprise databases, continued –Review tables, joins, queries –Restricting one’s view of entire database –Design considerations –Concurrency.
Requirements Gathering this process determines exactly what is required (and not required) of a project Three key areas include: Identify and prioritize.
Making a great Project 2 OCR 1994/2360. Analysis This is the key to getting it right. Too many candidates skip through this section. It’s worth 20% of.
Human Computer Interaction
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
Interviewing 1. Goals of Interviewing  Make sure that the biases and predispositions of the interviewer do not interfere with a free exchange of information.
Traceability, Change and Quality – Chapters Requirements Text Steve Chenoweth & Chandan Rupakheti RHIT Question 1.
Slide 1 Requirements Determination Chapter 5. Slide 2 Objectives ■ Understand how to create a requirements definition. ■ Become familiar with requirements.
Usability Assessment Methods beyond Testing Chapter 7 Evaluating without users.
Chapter 4 Collecting Requirements. What do you want to know? What is the problem area? How does the business you approach it? Is the data available? Who.
Ways of Collecting Information Interviews Questionnaires Ethnography Books and leaflets in the organization Joint Application Design Prototyping.
Information Gathering: Interactive Methods
Kendall & KendallCopyright © 2014 Pearson Education, Inc. Publishing as Prentice Hall4-1 Interactive Methods to collect Information Requirements Interviewing.
Session 9 Communicating with Parents: Parent-Teacher Conferencing.
Data Gathering Techniques 27 th February Data Gathering Techniques System requirements specify what the system must do or what property or quality.
Team Skill 2 Understanding User and Stakeholder Needs Interviewing (10)
Field Research: Conducting an Interview A workshop brought to you by the Purdue University Writing Lab.
Lecture 10 More Innovation SE3821 Software Requirements and Specification Dr. Rob Hasker (based on slides by Dr. Brad Dennis)
Primary Research Options Interview – One-on-one questions/answers with an expert – Often focuses on open-ended questions – Personal, Phone, Survey.
Storyboarding Steve Chenoweth & Chandan Rupakheti RHIT Chapters 13, Requirements Text and storyboarding web article.
HOW TO SUPPORT YOUR CHILD MATH HOMEWORK. PURPOSES OF HOMEWORK : Independent Practice – an opportunity for students to determine how well they understood.
Applying Use Cases to Implementation (Chapters 25,26 - Requirements Text) Steve Chenoweth & Chandan Rupakheti Question 1.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) Sriram Mohan.
Analyzing the Problem Continued and Product Features and Challenges Steve Chenoweth & Chandan Rupakheti RHIT Pages Requirements Text.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Basic Terms Research—the process of finding information relevant to a particular topic Source—any medium that provides information relevant to a particular.
Reference Interview Skills for Student Workers. What is a reference interview? “[a] Conversation between a member of the library reference staff and a.
Chapter 7 Researching Your Speech. Researching your speech: Introduction Researching your topic and providing strong evidence for your claims can make.
Week 2: Interviews. Definition and Types  What is an interview? Conversation with a purpose  Types of interviews 1. Unstructured 2. Structured 3. Focus.
Primary Research--Interviews 1)Roughly outline the progression of questions you’d like to ask –More efficient gathering of information –Reflects well on.
Cooper Goal-Directed Design: Practice Session Dr. Cindy Corritore Creighton University ITM 734 Fall 2005.
Systems Development Lifecycle Analysis. Learning Objectives (Analysis) Analysis Describe different methods of researching a situation. State the need.
[name] [demographic] [goals] A Template for Creating Buyer Personas.
A Marketer’s Template for Creating Buyer Personas [name] [demographic]
[name] [demographic] [goals] The Marketer’s Customer Persona Template.
The Marketing Research Process
A Marketer’s Template for Creating Buyer Personas [name] [demographic]
Designing for people CPSC 481: HCI I.
Business Model Validation Lab
Interviewing S.Vidya,AP/CSE.
Basic Research Terms Research—the process of finding information relevant to a particular topic Source—any medium that provides information relevant to.
Pitch deck Project Alpha
Interviewing Sriram Mohan.
Logo / branding / images
A Marketer’s Template for Creating Buyer Personas [name] [demographic]
Presentation transcript:

Personas & Interviewing Steve Chenoweth & Chandan Rupakheti RHIT Chapter 10 - Requirements Text Links to Personas ref’s on the web Quiz 3a, Question 10 Dorte is 53 years old and works as a secretary in her husband’s plumbing business in the suburbs of Copenhagen. There are 5-6 assistants and apprentices in the company.

Outline  Mistakes to avoid  Before the interview  Questions

Most Common Mistake  Lack of preparation  Bias

Context Free Questions  Who is the user?  Who is the customer?  Are their needs different?  Where else can a solution to this problem be found? Quiz 3a, Question 1

Outline  Mistakes to avoid  Before the interview  Questions

Where Should You Hold an Interview?  Non-threatening environment Customer's turf? Room large enough for group  Free from distractions

Interview Preparation  Do some research  Prepare questions  Prepare agenda  Select roles: Note taker Questioners  Don’t stop the user when they are trying to answer a question, don’t just follow the script, try and establish a rapport. Question 2

Interview Phases 1.Establish user profile 2.Assess the problem 3.Understand the environment 4.Recap for understanding 5.Analyst's inputs 6.Assess solution 7.Assess opportunity 8.Assess reliability, performance 9.Other requirements 10.Wrap-up

Outline  Mistakes to avoid  Before the interview  Questions See Fig 10-1 in the Requirements book Requirements engineers should all know standard questions like these, which are good things to ask in many interviews. E.g.,  “How will the software be distributed?”  “Is this the real problem?”  “How do you solve it now?”

1. Establish User Profile  Do some research first  Determine background of interviewee  Find out what will constitute success or failure

Personas – in software engineering  Personas or personae are fictitious characters that are created to represent the different user types within a targeted demographic that might use a site or product.  Used in HCI, Will they be useful for us? Why, If yes How? Right – Examples of personas used by IBM in development of mobile apps by an IT organization. Identifying roles is not good enough. You have to feel like you know a user personally as you develop their software. Ethnographic studies are now common.

2. Assess the Problem  Find out what the problems are  How are problems addressed now?

3. Understand the Environment  Find out about the users  Find out about the computing environment  How much help will users need?

4. Recap for Understanding  Paraphrase what you have heard so far  Is anything missing?

5. Analyst's Inputs  Ask about problems that you would expect to be present  Rank these problems relative to others

6. Assess Solution  What if...  How important would it be?

7. Assess Opportunity  Determine the market for the solution  Determine the value of the solution

8. Assess Reliability and Performance  Determine nonfunctional needs: reliability performance support

9. Other Requirements  Any external requirements?  Any other requirements not already mentioned?

10. Wrap-up  What should we have asked?  How can we follow up?

Why Not A Questionnaire Instead?...  …After all, they can be done so much more efficiently! But  Difficult to follow-up on responses  Relevant questions cannot always be designed in advance.  Advantages of interviews: Personal Contact Interaction/Follow-ups Questions 3-5