Unlock hundreds more features
Save your Quiz to the Dashboard
View and Export Results
Use AI to Create Quizzes and Analyse Results

OR
Sign inSign in with Facebook
Sign inSign in with Google
Quizzes > Business & Finance

Which Is Not a Characteristic of Elicitation? Quiz

Quick, free elicitation characteristics quiz. Instant results.

Editorial: Review CompletedCreated By: Ernest MontoyaUpdated Aug 24, 2025
Difficulty: Moderate
2-5mins
Learning OutcomesCheat Sheet
Paper art illustration on teal background inviting challenge with free CBAP elicitation techniques quiz

Use this quiz to identify what is not a characteristic of elicitation and check your understanding of common CBAP techniques. You will get instant results and brief explanations to target weak spots. If you enjoy spotting exceptions, try not a segmentation type, sharpen reasoning with not a critical thinking step, and practice classification with which of these is not.

Elicitation is characterized by all of the following except what?
Iterative discovery of information
Collaborative requirement gathering
Interactive dialogue with stakeholders
Passive one-way communication
Elicitation in business analysis is a dynamic and collaborative activity, not a passive one-way communication. It involves active engagement between the business analyst and stakeholders to discover needs. This two?way interaction is critical to ensure mutual understanding of requirements.
Which of the following is not true about when elicitation should occur in a project?
It should be a one-off activity at the project end.
It occurs whenever new information arises.
It is often revisited iteratively.
It starts early in the project lifecycle.
Elicitation is not confined to a single point in time or only at the end of the project. Effective business analysts begin elicitation early and revisit it iteratively as new insights emerge. This ensures requirements remain accurate and complete throughout the lifecycle.
Which statement does not describe a characteristic of effective elicitation?
It values stakeholder perspectives
It fosters open-ended questions
It encourages collaborative workshops
It requires no stakeholder involvement
Elicitation fundamentally depends on stakeholder involvement; without it, requirements cannot be validated or clarified. Effective elicitation leverages questions and workshops to draw out stakeholder input. Excluding stakeholders would undermine the entire process of capturing accurate requirements.
Elicitation is known for being all of the following except:
A one-way transmission of information
Focused on stakeholder engagement
Bidirectional communication
Adaptive to changing needs
Elicitation is a two?way, adaptive dialogue that involves continuous feedback from stakeholders. It is not a unilateral or one?way activity. The process should adapt to stakeholder insights and evolving project conditions.
Which of these is not a primary objective of the elicitation process?
Confirming understanding with stakeholders
Gathering detailed requirements
Finalizing project deployment plans
Clarifying stakeholder needs
Elicitation focuses on uncovering and clarifying requirements, not on finalizing deployment or release planning. Deployment planning is a separate activity later in the project lifecycle. Elicitation centers on gathering and validating stakeholder needs.
Which of the following is not an elicitation technique commonly used in business analysis?
Observing user activities
Performing root cause analysis
Conducting workshops
Interviewing stakeholders
Root cause analysis is an analytical technique used to diagnose problems rather than to elicit requirements. Interviews, workshops, and observation are direct elicitation techniques. Choosing the correct elicitation technique depends on the context and stakeholder availability.
Which of these is not typically managed during the elicitation planning phase?
Selecting appropriate techniques
Defining stakeholder roles
Establishing communication channels
Scheduling kick-off project meetings
Scheduling project kick-off meetings is part of overall project management rather than specifically elicitation planning. Elicitation planning focuses on identifying stakeholders, choosing techniques, and establishing how to communicate. Kick-off meetings set initial project alignment but are not an elicitation task.
Which of the following does not support effective elicitation session facilitation?
Assuming stakeholder knowledge is complete
Asking open-ended questions
Active listening
Use of visual aids
Assuming that stakeholders already have complete knowledge can lead to missed requirements and unchallenged assumptions. Effective facilitation relies on active listening, visual aids to clarify ideas, and open-ended questions to explore depths. Facilitators should verify and expand understanding rather than assume it.
Which is not a benefit of proper elicitation?
Reduced scope creep
Consistent project delays
Enhanced stakeholder alignment
Improved requirement quality
Proper elicitation improves requirement quality, aligns stakeholders, and helps control scope by uncovering hidden needs early. Consistent project delays indicate poor planning or risk management, not well-executed elicitation. Effective elicitation aims to streamline delivery rather than cause delays.
Which activity is not typically part of the conduct elicitation task?
Running focus groups
Applying brainstorming
Documenting meeting outcomes
Collecting feedback
Documenting meeting outcomes is usually part of the confirm and document tasks following elicitation, rather than the conduct activity itself. The conduct task focuses on engaging stakeholders through workshops, brainstorming, and feedback collection. Proper documentation follows once information has been gathered.
Which of the following is not an output of the Elicitation and Collaboration knowledge area?
Requirements documentation
Assumption log
Stakeholder requirements traceability matrix
Stakeholder register
The stakeholder register is an input to elicitation, identifying who to engage. Outputs include the documented requirements, assumption logs, and traceability artifacts. Elicitation and collaboration produce and refine requirement artifacts, not the stakeholder register.
Which sequence below does not reflect the recommended order of elicitation tasks in BABOK?
Plan elicitation > Prepare > Conduct > Document
Plan elicitation > Prepare > Conduct > Confirm
Plan elicitation > Conduct > Prepare > Confirm
Prepare > Plan elicitation > Conduct > Confirm
BABOK defines the proper order as plan elicitation, prepare for elicitation, conduct elicitation, and then confirm elicitation results. Starting with preparation before planning reverses the defined sequence. Maintaining the correct flow ensures structured and thorough requirements gathering.
Which is not considered a common challenge during elicitation sessions?
Stakeholder unavailability
Ambiguous terminology
Gold plating of solutions
Unclear business objectives
Gold plating refers to adding unnecessary features, which typically occurs during design or development, not during elicitation. Common elicitation challenges include unavailable stakeholders, vague objectives, and unclear terminology. Identifying and mitigating these issues ensures more effective requirement discovery.
Which is not recommended when eliciting requirements from remote stakeholders?
Recording sessions for later review
Distributing pre-read materials
Using video conferencing tools
Relying solely on unstructured email chains
Unstructured email chains often lead to confusion and lost information when eliciting remotely. Structured meetings, pre-reads, and recorded sessions support clarity and comprehensive information capture. Using reliable collaboration tools ensures effective engagement across distances.
Which of the following is not a characteristic of effective elicitation in highly ambiguous environments?
Flexibility to adapt techniques
Iterative prototyping with stakeholders
Strong focus on stakeholder collaboration
Strict adherence to a fixed process
In ambiguous environments, rigid processes can inhibit discovery and responsiveness to new insights. Effective elicitation relies on flexible methods, iterative feedback, and deep collaboration. Analysts must adapt approach and tools as understanding evolves.
0
{"name":"Elicitation is characterized by all of the following except what?", "url":"https://www.quiz-maker.com/QPREVIEW","txt":"Elicitation is characterized by all of the following except what?, Which of the following is not true about when elicitation should occur in a project?, Which statement does not describe a characteristic of effective elicitation?","img":"https://www.quiz-maker.com/3012/images/ogquiz.png"}

Study Outcomes

  1. Understand Elicitation Fundamentals -

    Grasp the core principles of elicitation and accurately identify which of the following is not a characteristic of elicitation.

  2. Differentiate Elicitation Traits -

    Analyze various attributes to distinguish valid characteristics from those that do not align with elicitation techniques.

  3. Apply Elicitation Techniques -

    Implement surveys, interviews, and observational methods effectively within business analysis elicitation questions.

  4. Evaluate Quiz Responses -

    Critically assess your performance in the elicitation techniques quiz to pinpoint areas for improvement.

  5. Analyze CBAP Elicitation Methods -

    Break down advanced CBAP elicitation methods to reinforce your expertise and prepare for certification.

  6. Identify Best Practices -

    Recall and apply industry best practices when tackling business analysis elicitation questions in real-world scenarios.

Cheat Sheet

  1. Define Clear Objectives with SMART Goals -

    Before you launch into elicitation, set Specific, Measurable, Achievable, Relevant, and Time-bound goals to keep sessions focused and productive. Industry bodies like IIBA (BABOK v3) emphasize goal-driven elicitation to align stakeholder expectations and deliverables. Mnemonic trick: remember SMART to avoid wandering discussions and wasted time.

  2. Choose the Right Elicitation Technique -

    Tailor your approach - interviews, surveys, workshops, and observations - to stakeholder availability and context, as outlined in BABOK's technique matrix. When you practice with an elicitation techniques quiz, note that surveys fit dispersed audiences while workshops are ideal for consensus-building. Example: Use an online survey for global teams and a facilitated workshop for co-located groups.

  3. Facilitate Neutrally and Avoid Bias -

    Neutral facilitation means banning leading questions and assumptions - essential for accurate data gathering. In CBAP elicitation methods or when asked "which of the following is not a characteristic of elicitation," recall that leading prompts or yes/no bias are not valid facilitation traits. Use the 5 Ws and 1 H (Who, What, When, Where, Why, How) to structure open-ended queries.

  4. Document and Model Requirements Precisely -

    Capture findings in clear artifacts - user stories, use case diagrams, or process flowcharts - following IEEE 830 or BABOK standards. A good practice is the user story template: "As a [role], I want [function], so that [benefit]" to ensure traceability and stakeholder clarity. This crisp documentation fuels downstream design and testing phases without ambiguity.

  5. Validate and Confirm with Stakeholders -

    After gathering input, run review sessions, prototypes, or walkthroughs to confirm accuracy and completeness. Stakeholder sign-off and feedback loops help you detect gaps early and strengthen buy-in - key steps in any business analysis elicitation questions scenario. Think "COV" (Confirm, Obtain buy-in, Validate) as your quick checklist for final sign-off.

Make a Quiz (FREE) Copy & Edit This Quiz Create a Quiz with AI

Marketing & Management Quizzes

Powered by: Quiz Maker