Requirements technology, also known as requirements engineering, is crucial for the successful development of systems. People understand it as the process of capturing and documenting the needs and expectations of all stakeholders. Effective requirements elicitation techniques are important to ensure that the end product aligns with the users’ and stakeholders’ needs. However, eliciting stakeholder requirements can be a challenging task due to differing opinions and priorities. This article discusses techniques for efficiently and effectively eliciting requirements from stakeholders. You can find further insights on eliciting stakeholder requirements below.
Interview Techniques for Stakeholder Requirements Elicitation
Among the most common and effective techniques for eliciting stakeholder requirements are interviews. It is very common among the stakeholder requirements elicitation techniques. People can conduct interviews in person, over the phone, or via video conference. The interviewer should prepare a list of questions beforehand. It is essential that the interviewee can express their needs and expectations freely and openly. Interviews are especially adept at revealing detailed requirements from individual stakeholders.
An interview is a formal or informal conversation between two or more individuals. One participant (the interviewer) poses questions to another (the respondent) to elicit information. For instance, an interviewer may seek to understand a specific perspective on a particular topic. Interviews occur in various formats, including in-person, by telephone, via video conference, or other electronic media.
Interviews facilitate obtaining information from witnesses or experts on a particular subject. Depending on the interview’s purpose and objectives, individuals can structure them as either structured or unstructured.
Structured Interviews
Structured interviews involve the interviewer asking a series of standardized questions. These questions aim to extract specific information from the respondent. Researchers and surveyors frequently use structured interviews because. Structured interviews enable them to ensure consistent and reliable data collection.
Unstructured Interviews
In contrast, unstructured interviews are more open. The interviewer asks open-ended questions and gives the respondent the opportunity to provide detailed answers. Unstructured interviews help gain insights and opinions on a specific topic.
In addition to the questions the interviewer asks, interviews can also include other components. These components are, for example, behavioral assessments, competency tests, or case studies. The mix of different components is crucial to the success of the individual project.
Interviews are a common and important tool for eliciting information. They can provide valuable insights and help companies make informed decisions about hiring, research, or other important activities.
Survey
Surveys are another powerful way to elicit stakeholder needs. You can conduct surveys online or through email. They prove particularly valuable when engaging a substantial number of stakeholders. Design them to capture specific information about stakeholder needs and expectations. Surveys can be particularly useful for eliciting quantitative data, such as the percentage of stakeholders who want a specific feature. Surveys are stakeholder requirements elicitation techniques with a social scientific scope.
A survey is a research method that collects data from a sample of people. The most common form of a survey is a questionnaire. People commonly use surveys in social science research, marketing, public opinion research, and many other fields. They are a powerful tool when it comes to requirements elicitation.
Types of Surveys
There are different types of surveys, including:
Cross-sectional surveys
These surveys collect data from a sample of people at a single point in time. People often use them to collect information about a specific demographic. Cross-sectional surveys examine relationships between different variables.
Long-Term Surveys
Surveys collect data from the same individuals over a period of time. You can use them to study changes in behavior or attitudes over time. Long-term surveys explore causal relationships between different variables.
Panel Surveys
Panel surveys collect data from the same individuals at multiple points in time. They are similar to cross-sectional surveys. However, unlike cross-sectional surveys, researchers often use panel surveys to study specific population groups or to track changes in behavior.
Cross-Sectional Panel Surveys
Cross-sectional panel surveys combine the characteristics of cross-sectional and panel surveys. They collect data from a sample of individuals at multiple points in time.
Steps in Gathering Requirements Through Surveys
The process of conducting a survey typically involves several steps, including:
Establishing the Research Question or Hypothesis
The first step in conducting a survey is to define the research question or hypothesis. This research question guides the study. Surveys collect the specific information. Additionally, the research question specifies that we will survey the population.
Designing the Survey Instrument
Once you define the research question, the next step is to design the survey instrument. This involves creating a questionnaire that we use for the surveys.
Sample Selection
The subsequent step is to select a sample of individuals to take the survey. The sample should be representative of the population to be studied and must also be large enough to provide reliable results.
Conducting the Survey
Various ways exist for carrying out surveys. For example, conducting surveys online, by post, by telephone, or in person. The choice of a method depends on the type of survey and the population to be studied.
Analyzing the Data
Analyzing data becomes possible when the survey is complete. The results provide insights to identify patterns and relationships between different variables. Statistical software can help analyze the data and identify significant results.
Surveys have several advantages as a research method. A key benefit is the ability to collect large amounts of data quickly and efficiently. They are also relatively easy to manage. Surveys can collect information on a wide range of subjects. However, surveys also have some limitations. These include the potential for response bias and the difficulty of measuring complex phenomena.
Surveys are a powerful tool for eliciting information about a population or group of people. When carefully planned and conducted, surveys can provide valuable insights into a wide range of topics. They help requirements engineers make informed decisions.
Focus Groups
The focus group method is one of the techniques for eliciting stakeholder requirements. A group of stakeholders comes together to discuss; this approach identifies needs and expectations. Focus groups can be particularly useful for identifying common themes and priorities among stakeholders. A qualified facilitator leads the group. A set of pre-determined questions should guide total sets. Focus groups are stakeholder requirements elicitation techniques for complex group dynamics.
Focus grouping is a research technique. Social sciences, marketing, and product development use this technique. It determines group opinions, attitudes, and perceptions on a specific topic or product. In requirements analysis, it is a powerful tool that requires careful planning and implementation. This technique involves bringing together a small group of people (usually 6-10). Such people have similar characteristics such as age, gender, education, and occupation. They then discuss a specific topic together in detail.
The main purpose of focus groups is to collect qualitative data on how people think and feel about a topic, product, or service. It also reveals what opinions they hold and why. The researcher moderates the discussion and guides the participants through structured and open discussions. This makes it possible to explore different points of view, experiences, and perspectives.
Key Features
Here are some key characteristics of focus groups:
Participants
As mentioned earlier, focus groups comprise of a small number of people who share similar characteristics. The selection of participants should be based on the research objective and the characteristics of the target population.
Moderator
A skillful moderator leads the discussion. They encourage participation and control the flow of the conversation. They also ensure that all participants have equal opportunities to make their contributions.
Framework
Focus groups usually take place at a neutral location, such as a conference room. The sessions typically last between 1 and 2 hours.
Recording
Audio or video recordings ensure to not overlook no comments or details. The names of the participants are not used. With this anonymization, participants can be confident that their data will only be used for requirements analysis.
Evaluation
After the session, the researcher transcribes and analyzes the data. They attempt to identify patterns, themes, and trends. Conclusions can be drawn from these findings.
Advantages
Focus groups are inexpensive. Participants are stakeholders who themselves have an interest in the success of the project. Focus groups provide rich and detailed data. They allow exploration of participants’ thoughts and feelings in a supportive and interactive environment.
Disadvantages
Focus groups are not representative of the general population. They can be influenced by group dynamics, social desirability, and facilitator bias. Such influences are difficult to anticipate, especially for external requirements engineers.
Focus groups are an effective way to understand the opinions and attitudes of a target audience. They offer valuable insights into how products, services, and topics are perceived and dealt with.
Workshops
The workshop method is one of the techniques for eliciting requirements from stakeholders. A group comes together to work on defining requirements for the software project. Workshops are specialized to generate ideas and set priorities. A qualified facilitator guides the group and encourages them to work together. The participants develop a common understanding of the requirements.
This eliciting technique is a method of obtaining information, ideas, or opinions from individuals or groups. Workshops are designed to facilitate the use of requirement techniques. Further they facilitate to elicit insights, ideas, or feedback from a group of participants. Workshops are useful stakeholder requirements elicitation techniques for distributed knowledge among many participants.
Proceed
In a requirements analysis workshop, a facilitator typically guides participants through a series of exercises. These exercises help to formulate their thoughts and opinions on a specific topic. These exercises can take many forms. Examples are brainstorming, group discussions, role plays, and much more.
The aim of a requirements elicitation workshop is to create an environment in which participants can openly share their ideas and opinions. This can be achieved by establishing ground rules for participation. These rules ensure that all participants have equal opportunities to contribute.
Trainers for survey method workshops often receive training in specific information elicitation techniques. They actively ask open questions, listen, and reflect on summaries. These techniques help them steer the discussion and make sure they include and hear all participants.
Context Dependency
Workshops on survey methods are used in a variety of contexts. Such contexts are, for example, product development, market research, organizational development, and other areas. The insights gained in these workshops can contribute to decision-making and drive innovation.
Eliciting technique workshops are a valuable tool for eliciting information and ideas from a group of participants. They raise requirements in a socially dynamic environment. Workshops can, therefore, be an effective means of promoting collaboration and creativity.
Prototyping
Prototyping is also one of the techniques for eliciting requirements from stakeholders. A prototype is a working model that is used, particularly in technical projects. Prototyping can be especially useful for obtaining feedback on the functionality and usability of the software. The prototype should be developed in cooperation with the stakeholders. The concept allows the testing of certain requirements and functions. Prototyping techniques are stakeholder requirements elicitation techniques which present ideas about the final product upfront.
It is a method used in various fields such as product design, software development, and research. Users, stakeholders, and experts provide feedback to the requirements engineers through usage. A prototype is an early version of a product or system. It is used to test and refine the design, functionality, and usability of the final product.
The prototyping process usually involves creating a mockup or working model of the product. This often has simplified features or functions. These enable usability, functionality, and user experience testing. The prototype can be made using a variety of materials and tools, including paper, cardboard, 3D printers, and software tools.
The technique of prototyping is an iterative process. Several versions of the prototype are created. Feedback is obtained at every stage of development. The feedback can come from different sources. Sources include users, stakeholders, and experts who can provide insight into the design, usability, and functionality of the product.
Feedback gleaned from the prototype helps refine the design, identify potential problems or questions, and improve overall usability. The process of prototyping and eliciting feedback helps ensure that the final product meets the needs and expectations of users and stakeholders.
Advantages
Some advantages of the prototyping technique are:
Faster development cycles
Using prototypes helps identify problems and refine designs early in the development process. This reduces the time and cost of subsequent changes.
Improved usability
Prototypes allow designers to test the user experience. They refine them to ensure the end product is intuitive and easy to use.
Better Stakeholder Engagement
Utilizing prototypes helps to engage stakeholders. They collect feedback to ensure that their needs and expectations are met.
Reduced Risk
Prototyping can assist in identifying potential issues and risks early in the development process. Thereby it helps reducing the likelihood of costly failures or delays.
Prototyping is a valuable tool for product designers, software developers, and researchers. It enables receiving feedback early in the development process and creating products that meet the needs and expectations of users and stakeholders.
Observation
Observation is also one of the techniques for eliciting stakeholder requirements. This can be done in person or via video conference. Observation is particularly useful for comprehending the context in which the software is intended to be used. It helps to pinpoint specific problems and challenges that stakeholders encounter in their work. Observation techniques are stakeholder requirements elicitation techniques which help to understand how users and other stakeholders actually work.
The observational technique is a research method that collects data by observing individuals or groups of people in a natural environment. This technique finds applications in various fields, including anthropology, psychology, and sociology.
Observation is the systematic recording and observation of the behavior and actions of individuals or groups in a specific context. The aim of observation is to elicit accurate and detailed data about a particular situation or behavior. The observational technique of inquiry is employed to obtain information from people in a natural and non-intrusive manner.
The observer can choose to observe actively or passively. In active observation, the observer can participate in the activity or situation being observed. In passive observation, the observer remains detached and observes from a distance.
Throughout the observation, the observer takes comprehensive notes on the behavior of the participants. This encompasses information about the spatial environment and all other pertinent details. For instance, the observer may use a recording device or video camera to document the observation.
Object of Study
The observational technique can be employed to gather a variety of data, including:
Verbal Behavior
This encompasses conversations, discussions, and other forms of verbal communication.
Nonverbal Behavior
This encompasses facial expressions, body language, and other nonverbal cues.
Group Dynamics
This includes the roles, relationships, and interactions among individuals in a group setting.
Environmental Factors
This encompasses the physical environment, lighting, and other factors that can impact behavior.
Advantages
The observational elicitation method has several advantages over other research methods. For example, it allows the observer to collect data in a natural environment, leading to more accurate and authentic data. Additionally, the observer collects data without directly influencing the behavior of the participants.
Limitations
However, there are also some limitations to the observation technique related to the survey. One limitation is that it can be time-consuming and expensive to conduct. Moreover, possible observer bias and subjective interpretation of the data can affect the results.
The research method of observation holds value for collecting data in a natural environment. Researchers can collect precise and genuine data about the behavior and interactions among individuals and groups. They elicit requirements while observing in a deliberate yet open-ended approach. However, it’s crucial to acknowledge the technique’s limitations. Researchers frequently blend it with other methods to attain a more holistic grasp of the situation under study.
Document Analysis
One technique for eliciting stakeholder requirements is document analysis. It entails examining current documentation like user manuals, business processes, and technical specifications. This approach proves valuable in pinpointing well-defined requirements. Moreover, it reveals any gaps or inconsistencies present in the existing documentation. Utilizing document analysis techniques as part of stakeholder requirements elicitation aids in obtaining a comprehensive understanding of the requirements.
Document analysis involves research methods that encompass the systematic study and interpretation of written, printed, or electronic materials. It is a valuable technique for obtaining information. Furhter it provides insights into various phenomena, such as social, cultural, political, or historical events. The technique of document analysis encompasses a set of activities aimed at uncovering the underlying meanings, patterns, and relationships in the examined documents. An important goal of document analysis is to extract relevant information from these documents.
Document analysis surveys refer to a collection of methods. Researchers use them to extract useful information from the documents they examine. These techniques encompass various approaches and aim to capture meanings, context, and relationships present in the documents.
Methods of document analysis
Content Analysis
Content analysis is the systematic study of a document’s content to identify and quantify specific themes, patterns, and relationships. It helps analyze the frequency and distribution of particular words, concepts, or ideas within the document.
Discourse Analysis
Discourse analysis involves examining the language and communication styles used in a document. This reveals patterns and relationships that reflect the social, cultural, or political context in which the document was created. Using discourse analysis, requirements engineers examine the meanings, assumptions, and values underlying the document.
Structural Analysis
This technique involves examining the organization and structure of the document to identify patterns and relationships. These patterns and relationships thus reflect the purpose and audience of the document. Through structural analysis, the underlying logic of the document and the assumptions that shape it can be uncovered.
Historical Analysis
Historical analysis involves examining the historical context in which each document was created. It also reveals patterns and relationships that reflect the social, cultural, or political forces that influenced the creation of the document. Historical analysis examines the meaning and impact of the document.
Comparative Analysis
Comparative analysis involves examining multiple documents to identify patterns and relationships. These patterns and relationships reflect similarities and differences. Comparative requirements analysis helps examine the underlying meanings, assumptions, and values that inform the examined documents.
Document analysis includes a set of methods designed to extract useful information from the examined documents. These techniques encompass a range of approaches aimed at capturing the meaning, context, and relationships present in the documents. By using survey techniques with document analysis, researchers generate deeper insights into the phenomena they study.
Brainstorming
Brainstorming is also one of the techniques for eliciting stakeholder requirements. In group discussions, participants develop ideas and solutions. Brainstorming is especially useful for generating new ideas and finding creative solutions to problems. The group is encouraged to freely express their ideas, and no idea should be discarded without careful consideration.
Brainstorming is a group creativity method. It serves to develop a large number of ideas in a short time. Advertiser Alex Osborn first introduced the technique in the 1940s. He believed that brainstorming in a group can generate more and better ideas than an individual working alone. The brainstorming technique is a stakeholder requirements elicitation technique for creative production.
Ground Rules
The main goal of brainstorming while using requirements elicitation techniques is to generate as many ideas as possible. There is no assessment or evaluation. To achieve this goal, the technique usually follows four basic rules:
Generate as many ideas as possible
Participants are encouraged to think outside the box and come up with as many ideas as possible. It doesn’t matter how unconventional or seemingly stupid these ideas may be.
Hold back your judgments
During the brainstorming session, it’s important not to engage in criticism, evaluation, or analysis of ideas. Instead, participants should actively avoid critiquing or dismissing any ideas during this stage of the process.
Encourage wild ideas
Creative, unconventional thinking is encouraged during brainstorming. Participants propose wild and unconventional ideas.
Build on the ideas of others
Participants should build on and improve the ideas of others. Instead of trying to develop completely new concepts yourself, everyone should benefit from each other.
***
During brainstorming, the moderator asks open-ended questions or gives hints to stimulate the flow of ideas among the participants. The facilitator uses various techniques, such as mind mapping, association, and wordplay, to help participants generate and share ideas.
The facilitator can also use different variants of brainstorming. Take e.g. reverse brainstorming, where the group thinks about ways to make a problem or situation worse. Another concept is brainwriting, where participants write down their ideas instead of verbally communicating them.
Brainstorming is a valuable technique for generating creative ideas. It encourages teamwork, and stimulating the participation and engagement of all group members. By using this technique, the moderators ensure that all participants have an opportunity to contribute. The group develops a wide range of ideas that can later be further developed and refined.
Conclusions
In summary, the stakeholder requirements elicitation techniques are an important part of software development. Using a combination of techniques such as interviews, surveys, focus groups, workshops, prototyping, observation, document analysis, and brainstorming, we ensure effective requirements elicitation. These techniques help elicit the information needed to design a system that meets stakeholder needs and expectations. It’s important to remember that each technique has its own strengths and weaknesses. The choice of techniques should be tailored to the specific needs of the project and its requirements.
Credits: Photo by Artem Podrez from Pexels