Interviewing S.Vidya,AP/CSE.

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

ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
Understanding User and Stakeholder Needs
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.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) CSSE 371, Software Requirements and Specification Don.
Brainstorming and Idea Reduction
BSBMKG506B Plan market research Session 1
Brainstorming - Creative Problem Solving Method Halka Baláčková, MBA Masaryk Institute of Advanced Studies, Czech Technical University in Prague
Team Skill 2 Understanding Stakeholders Needs
Brainstorming Steve Chenoweth & Chandan Rupakheti RHIT Chapters 12 & 13, Requirements Text, Brainstorming Techniques document Brainstorming involves generating.
Soft Skills for a Digital Workplace: Verbal Communication Unit D: Improving Informal Communication.
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 5: Understand Stakeholder Needs.
 The model consists of 6 steps: Step 1: Define the problem or opportunity. Step 2: Set objectives & criteria. Step 3: Generate alternatives. Step 4:
Requirements Elicitation Techniques. Interviewing and questionnaires.
Personas & Interviewing Steve Chenoweth & Chandan Rupakheti RHIT Chapter 10 - Requirements Text Links to Personas ref’s on the web Quiz 3a, Question 10.
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.
Interviewing 1. Goals of Interviewing  Make sure that the biases and predispositions of the interviewer do not interfere with a free exchange of information.
© ABSL Power Solutions 2007 © STM Quality Limited STM Quality Limited Brainstorming TOTAL QUALITY MANAGEMENT Brainstorming.
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 Interviewing (10)
Lecture 10 More Innovation SE3821 Software Requirements and Specification Dr. Rob Hasker (based on slides by Dr. Brad Dennis)
Working Technologically Early Stage 1 – Stage 3. Students evaluate by: recounting the steps taken to reach a final solution discussing their likes and.
1 Team Skill 2 - Understanding User and Stakeholder Needs (Chapters 8-13 of the requirements text) Sriram Mohan.
1 Week 8 - Life cycle vs Methodology IT2005 System Analysis & Design.
Software Requirements and Design Class 4 Khalid Ishaq.
Finding & Solving Customers’ Problems Dr. M. Gunawan Alif.
SWE 214 (071) Chapter 12: Brainstorming and Idea Reduction Slide 1 Chapter 12: Brainstorming and Idea Reduction.
TEAM BUILDING. WHY IS TEAM BUILDING IMPORTANT? YOUR ABILITY TO GET ALONG WITH OTHER PEOPLE, AND USING TEAMWORK WILL LARGELY DETERMINE HOW SUCCESSFUL YOU.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
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.
4 Chapter 4: Beginning the Analysis: Investigating System Requirements Systems Analysis and Design in a Changing World, 3 rd Edition.
From: A. Cooper et al.: About Face Andreas Rudin
Interviews & focus groups
Design and modeling 10 step design process
Pass4itsure Microsoft Dumps
Effective Meetings Chapter 8.
Pass4itsure Microsoft Dumps
Demonstrate appropriate creativity (PD:012, QS LAP 5)
10.2 Qualitative research: Interviews
IENG 451 / 452 Voice of the Customer: Analysis (KANO, CTQ)
Brainstorming - Creative Problem Solving Method
Interviews & focus groups
CS 790M Project preparation (I)
Chapter 3: The Requirements Workflow
Investigating System Requirements
Knowledge Utility results from Rigor in Methods & Relevance in Content
MIT GSL 2018 week #1 | day 4.
Turning data insights into action
Innovation in your hands
Dr Elaine Stewat 15th-16th May 2018
ACTION LEARNING THEORY IN MANAGEMENT
Lesson 15: Coaching Skills
Creative Design Solutions: Design Thinking
Employee engagement Delivery guide
Interviews & focus groups
Lesson 15: Coaching Skills
Interview Preparation Workshop
Solving Workplace Problems
Interviewing Sriram Mohan.
Interviews & focus groups
Solving Problems in Groups
Creative Design Solutions: Design Thinking
1.02 Creative Design Solutions: Design Thinking
CS 426 CS 791z Topics on Software Engineering
Creative Problem Solving Method Dr Mohd Razali Maarof.
CS 426 CS 791z Topics on Software Engineering
Innovation Challenge Every business starts with an idea, but to be successful you need more than just a good idea. Starting from a common challenge question,
Presentation transcript:

Interviewing S.Vidya,AP/CSE

S.Vidya,AP/CSE

Overview Technique Good for Kind of data Plus Minus Interviews Exploring issues Some quantitative but mostly qualitative data Interviewer can guide interviewee. Encourages contact between developers and users Time consuming. Artificial environment may intimidate interviewee S.Vidya,AP/CSE

Define interviewing? Interviewing is a simple and direct technique. Context-free questions can help achieve bias-free interviews. Then, it may be appropriate to search for undiscovered requirements by exploring solutions. S.Vidya,AP/CSE

Context Free Questions These questions focus us to listen before attempting to describe the solutions. Eg: Who is the user? Who is the customer? Are their needs different? S.Vidya,AP/CSE

Context Free Questions Context free questions are questions that can be used regardless of the project under consideration. They are general questions about the nature of the project and the environment in which the final product will be used. Context free questions make sense at several stages of an interview. S.Vidya,AP/CSE

Solutions - context questions Search for the undiscovered requirements Providing solutions to appropriate problems-problems being solved In addition provides insights of the problem Different views of the problem S.Vidya,AP/CSE

Tips for successful Interview Prepare appropriate questions and review the questions before interview Before interview research the background of the Stakeholders and Company Don’t bore the person being interviewed with the questions Jot down the answers in your notebook during interview Refer the template during the interview S.Vidya,AP/CSE

Template Part 1: Part 2: Part 3: Part 4: Part 5: Establishing the customer or user profile Part 2: Assessing the Problem Part 3: Understanding the user Environment Part 4: Recap for Understanding Part 5: The analyst’s input on the customers problem S.Vidya,AP/CSE

Template Part 6: Part 7: Part 8: Part 9: Part 10: Part 11: Assessing your solution Part 7: Assessing the opportunity Part 8: Assessing the reliability , performance and support needs Part 9: Other requirements Part 10: Wrap up Part 11: The analyst’s summary S.Vidya,AP/CSE

Brainstorming S.Vidya,AP/CSE

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: uncertain There is little expertise for the type of applications Innovation is important (e.g., novel system) Two main activities: The Storm: Generating as many ideas as possible (quantity, not quality) – wild is good!(brainstroming ) The Calm: Filtering out of ideas (combine, clarify, prioritize, improve…) to keep the best one(s) – may require some voting strategy(idea reduction) Roles: scribe, moderator,participants S.Vidya,AP/CSE

Brainstorming – Objectives Hear ideas from everyone, especially unconventional ideas Keep the tone informal and non-judgemental Keep the number of participants “reasonable“ – if too many, consider a “playoff “-type filtering and invite back the most creative to multiple sessions Encourage creativity Choose good, provocative(challenging) project name. Choose good, provocative problem statement Get a room without distractions, but with good acoustics(audiability), whiteboards, coloured pens, provide coffee/donuts/pizza/beer S.Vidya,AP/CSE

Brainstorming – Roles Scribe Moderator/Leader Write down all ideas (may also contribute) May ask clarifying questions during first phase but without criticizing Moderator/Leader Cannot be the scribe leadership role S.Vidya,AP/CSE

Brainstorming – Participants Virtually any stakeholder, e.g. Developers Domain experts End-users Clients ... “Ideas-people” – a company may have a special team of people Chair or participate in brainstorming sessions Not necessarily further involved with the project S.Vidya,AP/CSE

Brainstorming – The Storm Goal is to generate as many ideas as possible Quantity, not quality, is the goal at this stage Look to combine or vary ideas already suggested No criticism or debate is permitted – do not want to inhibit participants Let your imagination soar Mutate and combine ideas S.Vidya,AP/CSE

Idea reduction Brainstorming idea- generation Phase Pruning Ideas Grouping Ideas Defining features Prioritizing ideas S.Vidya,AP/CSE