Price: $1,999.00
Length: 2 Days
Print Friendly, PDF & Email

Eliciting Stakeholder Requirements Training

A stakeholder is anyone who has direct or indirect influence on the requirements. This could include end-users, managers, system engineers, test engineers and maintenance engineers, etc.

The purpose of stakeholder needs and requirements definition activities is to elicit a set of clear and concise needs related to a new or changed mission for an enterprise, and to transform these stakeholder needs into verifiable stakeholder requirements.

Normally four steps are involved in this process:

  1. Requirements discovery — This is the process of interacting with, and gathering the requirements from the stakeholders. It can be done through interviews, scenarios and prototypes.
  2. Requirements classification and organization — The relationship among components is defined in this step. What is done here will help in the decision of identifying the most suitable architectural design patterns.
  3. Requirements prioritization and negotiation — Multiple stakeholders usually equals multiple conflicts. In this step all stakeholder requirements should be taken into consideration and then prioritized.
  4. Requirements specification — Requirements are documented.

Stakeholder requirements play major roles in systems engineering, because they:

  • Form the basis of system requirements activities.
  • Form the basis of system validation and stakeholder acceptance.
  • Act as a reference for integration and verification activities.
  • Serve as means of communication between the technical staff, management, finance department and the stakeholder community.

Eliciting Stakeholder Requirements Training Course Specifics

Eliciting Stakeholder Requirements training course provides the key concepts of stakeholder requirements elicitation. It introduces various tools and methods of collecting information and requirements from project’s stakeholders. Participants also learn about the common challenges, disadvantages and concerns associated with each method and technique.

Target Audience

  • Project managers
  • Project engineers
  • Business analyst
  • All individuals who are involved in the processes of collecting data and eliciting requirements in various projects

Training Objectives

Upon the completion of eliciting, collecting and developing requirements workshop, the attendees can:

  • Identify relevant stakeholders and other sources of information for each high-level requirement
  • Plan to elicit accurate requirements and classify them
  • Create a framework to identify stakeholder needs and requirements
  • Choose appropriate tools for requirements collection and determine the rationale for their selection
  • Elicit thorough, accurate, and traceable requirements by applying different tools
  • Conduct interviews with stakeholders to analyze and validate their needs
  • Learn about various communication skills to interact with stakeholders
  • Gather a complete set of requirements based on the business needs and stakeholder goals in order to meet project objectives
  • Conduct requirement workshops to assist hard data collection and documentation of the requirements
  • Define the capability scope
  • Apply best practices of data elicitation

Course Outline

Overview of Eliciting, Collecting and Developing Requirements

  • Eliciting requirements definition
  • Basics of eliciting requirements
  • Definition of requirements
  • Issues of elicitation
  • Gathering and documenting requirements
  • Agile requirements development
  • Eliciting methods and techniques

Requirements Elicitation Problems

  • Problems of scope
  • Problems of understanding
  • Problems of volatility

Elicitation Techniques

  • Information gathering
  • Requirements expression and analysis
  • Verification and validation

Elicitation Methodology Frameworks

  • Requirements elicitation process model
  • Methodology
  • Integration of techniques
    • Fact-finding
    • Requirements gathering
    • Analysis and rationalization
    • Prioritization
    • Integration and validation
  • Criteria assessment

Eliciting Tools

  • Hard data gathering
  • Interviews
  • Questionnaire
  • Group techniques
  • Participant observation
  • Ethnomethodology
  • Knowledge elicitation techniques

Traditional Elicitation Approaches

  • Introspection
  • Reading existing documents
  • Analyzing hard data
  • Interviews
  • Surveys / Questionnaires
  • Meetings

Hard Data Collection

  • What is considered as hard data?
  • Sampling methods
    • Purposive sampling
    • Random sampling
    • Stratified random sampling
    • Clustered random sampling
  • Size of sampling
  • Sampling process

Interviews

  • Types of interview
    • Structured
    • Open-ended
  • Advantages
    • Rich collection of data
    • Good for uncovering opinions, feelings, goals, as well as hard facts
    • Can probe in-depth, & adapt follow up questions to what the person tells you
  • Drawbacks
    • Hard to analyze a great amount of qualitative data
    • Hard to compare various respondents
    • Interviewing is a challenging skill
  • Concerns
    • Unanswerable questions
    • Implicit information
    • Removal from context
    • Interviewer’s attitude may cause bias
  • Some useful tips
    • Starting off tips
    • Obtain permission to record the interview
    • Ask the straightforward questions first
    • Follow up interesting leads
    • Leave open-ended questions for the end

Questionnaires

  • Advantages
    • Can quickly gather info from large numbers of people
    • Can be managed remotely
    • Can gather manners, beliefs, characteristics
  • Disadvantages
    • Simplistic categories generate so little material
    • No chance for users to take their real needs
  • Concerns
    • Bias in sample selection
    • Bias in self-selecting respondents
    • No statistical significance
    • Open-ended questions are difficult to analyze
    • Leading questions
    • Appropriation
    • Vague questions

Group Elicitation Approaches

  • Categories
    • Focus Groups
    • Brainstorming
  • Advantages
    • Better communication than formal interview
    • Can gauge reaction to stimulus materials
  • Disadvantages
    • Can create unnatural groups
    • Danger of Groupthink
    • May only provide superficial responses to technical questions
    • Requires a highly trained facilitator
  • Concerns
    • Sample bias
    • Dominance and submission

Joint/Rapid Application Development Principals

  • Group dynamics
  • Visual aids
  • Organized, rational process
  • WYSIWYG documentation method

Participant Observation Technique

  • Approach applications
  • Advantages
    • Contextualized;
    • Reveals details that other methods cannot
  • Disadvantages
    • Extremely time consuming
    • Resulting ‘rich picture’ is hard to analyze
    • Cannot say much about the results of proposed changes

Elicitation Models

  • Waterfall model
  • Spiral model
  • Agile model
  • Using multiple models

Elicitation Best Practices

  • Use your interpersonal skills
  • Always think broadly
  • Be prepared
  • Determine and manage stakeholders
  • Identify the root cause of the problem
  • Define the capability scope
  • Extract and elicit requirements from all the available sources
  • Categorize the type of documents and requirements
  • Model the requirements for validation
  • Rank the requirements based on their importance
  • Obtain final agreement from contributing stakeholders
  • Document the requirements for final approval

Eliciting, Collecting and Developing Requirements Workshop

  • Stakeholder requirements play major roles in systems acquisition
  • Stakeholder Needs and Requirements activities
  • To elicit a set of clear and concise needs
  • Process Approach
  • Activities of the Process
  • Artifacts, Methods and Modeling Techniques
  • Practical Considerations

 

Eliciting Stakeholder Requirements Training

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.