Elicitation Techniques for Business Analysis

By Kadir Çamoğlu

One of the most important prerequisites for a successful IT software project and the right software solution is to conduct an effective business analysis. A good business analysis is only possible with the right techniques. Especially to support analysts at the beginning of their careers, I have written the book "Necessities Revealing Techniques for Business Analysts" as a supporting reference to carry out successful business analysis studies by filtering over 25 years of software projects, software process consultancy, and corporate training experiences in a pot.

 

The book contains the most common techniques used to reveal business analysis information, especially requirements. Techniques are discussed in detail with the titles of what they are, how they are applied, success factors, and important points about use.

 

What Will You Learn?
• Elicitation
• Document Analysis Technique
• Interview Technique
• Interface Analysis Technique
• Focus Group Technique
• Workshop Technique
• Brainstorming Technique
• Observation Technique
• Prototyping Technique
• Survey Technique
• Reverse Engineering Technique

 

Who should read this book?
This target audience is anyone who performs analysis in software solutions, no matter what is written on the business card. The following audiences will benefit most from this book:
• Analysts
• System Analysts
• System Engineers
• Requirements Engineers
• Business Analysts
• Process Analysts
• Web Designers
• User Experience Designers
• Developers
• Test Experts
• Project Managers
• Demand Managers
• Service Managers
• Consultants
• Solution Developers
• Product Managers
• Scrum Masters

• Language: English
• Publisher: Kadir Çamoğlu
• Release date: Sep 5, 2022
• ISBN: 9798215012536

Kadir Çamoğlu

Kadir Çamoğlu (Ph.D., Computer Engineering), is a problem solver, consultant, teacher, author,  practitioner, and architect of system and software solutions. Over the past 25 years, he has worked in every phase of the software development life-cycle. Kadir, who has been particularly focused on software quality and processes for the last 10 years, has published 13 books in Turkish in print and electronic formats in this field. He also holds the CBAP, PMP, PSM I, CSM and CSPO certifications. [e-mail]

Book preview

Introduction

Elicitation work means receiving, collecting, and getting information from stakeholders or other sources of need. This is the most basic and important method for identifying requirements.

Elicitation work can be planned or unplanned. For example, you may identify needs by conducting planned needs workshops or focus group work with specific stakeholders. Or you may meet with a stakeholder and during the conversation, some requirements may emerge. As a good analyst, prepare for both situations and use them as needed.

Determining the elicitation approach and planning the work is done in the phase where the analysis is planned. In this phase, information obtained about the stakeholders and other sources of requirements is used to determine which stakeholder and issue to work with and which requirements gathering techniques to use. In the later phases of the analysis, the approaches to the associated activities are reviewed and updated as necessary as the elicitation work approach.

After you clarify the elicitation approach, make the necessary preparations. This phase includes work such as informing relevant stakeholders for the study, allocating and preparing the necessary resources.

When the preparations are completed and the time is right, you carry the elicitation activity out. In this phase, activities such as ensuring stakeholder participation and involvement in the study, adherence to the scope of the study and fulfillment of its purpose and note-taking on the issues discussed are conducted.

After the study, the analyst records the information obtained in writing based on his notes. He checks the prepared document in terms of content and form and gets it ready to be sent for confirmation.

After the elicitation work, the written analysis information is sent to the stakeholders who took part in the corresponding study and if there is any suggestion for correction, you will receive their confirmation.

After stakeholder feedback, any necessary corrections are made, and finally, the newly obtained analysis information is shared with other stakeholders.

Be mindful of the following when gathering business analysis information:

•  Constantly question what the change is that you are in and how it is occurring during analysis information acquisition activities. (By chance, we mean the change that will occur in the company).

•  Since the process of elicitation is iterative in nature, the level of understanding required will increase as the studies progress. Therefore, do not be under the illusion that you have a very clear understanding of the need from the beginning. Focus on clarification and revisit it as the work progresses.

•  Try to understand the solution components needed throughout the analysis and elicitation process.

•  Seek to understand the relative value of the information you get in your studies and seek stakeholder opinion on that value.

•  Track all internal and external factors that could affect the solution and project and see if there are any changes to your current determinations.

Determining the Elicitation Approach

Determining the elicitation approach is the stage of determining what techniques we will use in elicitation, how stakeholder participation will be ensured, what activities will be undertaken, and in what order. Determining the elicitation approach should begin in the planning phase of the analysis. As the timing of elicitation comes, it is useful to review the approach and revise it if necessary.

By establishing an effective approach, you can make better use of stakeholders' time and better ensure their participation in the project. This will make your analysis activities more successful and on schedule. This will further increase the likelihood of successful product delivery.

To identify approaches to requirements gathering, consider the following topics:

•  What analysis information should be obtained? (Requirements, process flows, business rules, screen prototypes, etc.).

•  From whom or where can you obtain the information you seek? (Domain expert, end user, sponsor, etc.)

•  How can you obtain information from relevant sources? (Personal interviews, workshops, observations, etc.)

•  When should you do the work? (Your availability, stakeholder's availability, resources for the meeting, etc.)

One of the most important elements of an effective analytical approach to knowledge gathering is that you do not take unnecessary time away from stakeholders. Seeing that your work is effective and appropriate will have a positive impact on the support and time stakeholders will give you.

In conclusion, it is important to consider the entire analysis process, the stakeholders, the project, and the product as a whole when planning your approach to gaining analysis knowledge. Plan by trying to see the big picture before moving on to the detailed work.

Preparing for Elicitation Work

Preparing elicitation work involves organizing the necessary resources, planning calendars, preparing the materials, and informing people. The goal of any elicitation work is to ensure that the activity to be conducted is most efficient for everyone involved, especially you.

During the preparation phase, consider:

•  The purpose and scope of the particular study should be clarified. (The requirements of module X will be detailed, or the first drafts of the mobile software screen prototypes will be defined, etc.

•  It should be clarified what technology or techniques will be used in the study. (Although the techniques to be used in the design have been established, they may be revised at this stage if deemed necessary.)

•  It should be determined who the participants will be. (Perhaps new stakeholders have joined the project or some of the existing stakeholders are not available.)

•  Materials to be used in the meeting should be prepared. (Projection, flipchart, white-board, camera, etc.).

•  Participants should be reminded of. (Format, location, date, time of the meeting, what is expected of participants in each work, etc.)

•  You should send the work agenda and relevant documents to participants.

•  If possible, the questions to be asked of participants should be determined in advance.

•  Depending on the agenda, a schedule for the activity should be prepared.

Performing Elicitation Work

Elicitation work is the activity