1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain standards for the practice of business analysis and for the certification of its practitioners

2 Who We Are The IIBA is an international non-profit professional association for business analysis professionals.

3 IIBA Goals  Create and develop awareness and recognition of the value and contribution of the role of the Business Analysis Professional  Define the Body of Knowledge  Define the business analysis profession by providing certification to its members  Provide a forum for knowledge sharing

4 Chapter Membership  Networking with other business analysis professionals  Informational speakers on relevant topics  Exposure to tools and techniques

5 IIBA Membership Types  Individual Membership  Corporate Membership

6 IIBA Membership Benefits  Free access to:  Personal Use of Membership Logo and Trademark as a "Member of the International Institute of Business Analysis™"  BABOK  Educational webinars  Professional forums to learn from experts and build reputation  Newsletter with current information  Lower fee for CBAP exam

Requirements Elicitation Presented by: Mariam Armia Keriakos Senior Systems Analyst Link Development, OTVentures 7

Agenda 1.What is Requirements Elicitation? 2.Requirements Elicitation Techniques 3.Tips for Choosing the Appropriate Technique 8

What Is Requirements Elicitation?  Sometimes referred to as requirements gathering  The practice of obtaining the requirements of a system from users, customers, and other stakeholders 9

Requirements Elicitation Input  Business case  Business need  Solution scope  Stakeholders list, roles, and responsibilities

Requirements Elicitation Activities 11  Choose the appropriate technique  Clarify the scope of the selected technique  Schedule all resources  People  Facilities  Equipment  Notify appropriate parties of the elicitation plan  Conduct the elicitation  Organize, analyze, and document elicitation results  Confirm elicitation results com com

Requirements Elicitation Techniques  Brainstorming  Document analysis  Focus groups  Interface analysis  Interviews  Observation  Prototyping  Requirements workshops  Survey/Questionnaire

RE- Brainstorming (1|2)  What is brainstorming?  Brainstorming focuses on a topic or problem to come up with many possible solutions  Is done in groups and utilizes the creativity of all group members  When to use brainstorming?  Produce numerous new ideas  Derive themes for further analysis 13

RE- Brainstorming (2|2)  Steps of Brainstorming  Define the interest area  Set expectations  Establish evaluation criteria  Share ideas  Rate Ideas 14

RE- Document Analysis (1|2)  What is document analysis? Analysis of all up to date documents that will affect the new solution (e.g. business plans, market studies, RFP, work statements, etc…)  When to use document analysis?  Plenty of available documentation  Objective is to gather details of existing solutions that will be inherited in new solutions  If SME are no longer available 15

RE- Document Analysis (2|2)  Document Analysis Stages  Evaluate which systems to investigate and which documents  Study the material  Confirm details with SME 16

RE- Focus Groups (1|2)  What are focus groups? Sessions where prequalified participants share their impressions, preferences, and needs guided by a moderator  When to use focus groups? Elicit ideas about a specific product, service, or opportunity 17 newbusinessservices.co.uk

RE- Focus Groups (2|2)  Stages of Focus Groups  Choose topic  Invite attendees  Run the focus group session  Produce report 18 newbusinessservices.co.uk

RE- Interface Analysis (1|2)  What is interface analysis? Identification of how will the system interact with its users satisfying their needs  When to use interface analysis? To identify user interface or interfaces between solutions 19

RE- Interface Analysis (2|2)  Stages of Interface Analysis  Identify needs of systems stakeholders  Describe purpose of the interface  Try a mock up with the stakeholders  Collect their feedback 20

RE- Interviews (1|2)  What are interviews? A systematic approach to elicit information from a person or a group in a formal or informal setting through;  When to use interviews?  Topic of the interview is specific  Detailed information are needed  Small number of stakeholders 21 jobinterview-questionsandanswers.com

RE- Interviews (2|2)  Stages of an interview  Identify potential interviewees  Design the interview  Conduct the interview  Post follow up and confirmation 22 jobinterview-questionsandanswers.com

RE- Observation (1|2)  What is observation? A means of eliciting requirements by conducting an assessment of the stakeholder’s work environment  When to use observation? When documenting details about current processes or if the project is intended to enhance or change a current process 23

RE- Observation (2|2)  Stages of Observation  Determine sampling of users  Introduce the observer  Conduct observation  Post observation wrap up Documentation and confirmation 24

RE- Prototyping (1|2)  What is prototyping? Details user interface requirements and integrates them with other requirements such as use cases, scenarios, business rules  When to use prototyping?  When the stakeholders lacks visualizations of what they want to have  When interaction and feedback is crucial 25

RE- Prototyping (2|2)  Stages of Prototyping  Determine the prototyping approach  Show the prototype  Storyboard  Screen prototypes  A Screen layout/Mock up  Evaluate the prototype 26

RE- Workshops (1|2)  What are requirements workshops? A focused event attended by carefully selected stakeholders and SMEs  When to use requirements workshops? When we need scope, discover, define, prioritize, and reach closure on requirements of a target system 27

RE- Workshops (2|2)  Workshop Stages  Classify stakeholders needs  Define purpose of the workshop  Define the agenda  Invite the attendees  Conduct requirements workshop  Wrap up 28

RE- Survey/Questionnaire (1|2)  What are surveys/questionnaires? A set of written questions to stakeholders and SMEs  When to use surveys/questionnaires?  Information is dispersed at many stakeholders  The stakeholders are not within the same location  We need to collect information anonymously  Information must be gathered in a relatively short time 29

RE- Survey/Questionnaire (2|2)  Survey/Questionnaire stages  Define the purpose of the survey  Identify the target group  Choose the appropriate survey type  Write the survey questions  Test the survey  Distribute the survey  Document the results 30

Technique Selection Criteria (1|2)  Target of the exercise  Scoping  High level requirements elicitation  Detailed requirements elicitation  Business process improvement  Else….  Stakeholders  The number of stakeholders  Their locations  Their background  The relationship between the different stakeholders 31

Technique Selection Criteria (2|2)  Time Factor How much time is dedicated for the requirements elicitation  Cost Factor How much money is dedicated for the requirements elicitation  Required Output Data  Quantitative data  Qualitative data  Behavioral data 32

References  IIBA BABOK Chapter 3  IIBA BABOK Chapter 9 33

Q&A 34

Thank You 35