First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Business Analysis Planning and Monitoring
Which business analysis activity is primarily concerned with defining how requirements will be elicited, documented, and approved before the work begins?
- Requirements life cycle management
- Business analysis planning and monitoring Correct answer.
- Strategy analysis
- Solution evaluation
Explanation
Business analysis planning and monitoring covers organizing the approach to the work itself, including how requirements will be elicited, analyzed, documented, and approved. It is a governance and organization activity rather than the execution of elicitation, strategy, or evaluation. The other knowledge areas apply the plan once it exists.
Question 2Business Analysis Planning and Monitoring
A business analyst is determining which stakeholders can approve changes to requirements. Which planning element is being defined?
- Business analysis information management approach
- Governance approach Correct answer.
- Stakeholder engagement approach
- Requirements traceability approach
Explanation
The governance approach specifies decision-making authority, including who approves requirements and how changes are authorized. Stakeholder engagement concerns collaboration and communication, while information management concerns storage and reuse. Traceability concerns relationships among requirements, not approval rights.
Question 3Business Analysis Planning and Monitoring
During planning, a business analyst maps each stakeholder's influence, attitude, and level of interest. What is the most appropriate purpose of this analysis?
- To estimate the total cost of the project budget
- To decide which stakeholders should be excluded from all future communication
- To tailor communication and collaboration activities to each stakeholder Correct answer.
- To rank stakeholders so that only executives receive requirements
Explanation
Stakeholder analysis in planning informs the engagement approach, allowing communication and collaboration to be tailored to influence, interest, and attitude. It does not justify excluding people or restricting information to executives. Cost estimation is a separate project management concern.
Question 4Business Analysis Planning and Monitoring
What is the main purpose of the business analysis information management approach?
- To assign project tasks to developers
- To define how business analysis information will be stored, accessed, and reused Correct answer.
- To determine the organization's strategic goals
- To test whether a delivered solution meets its objectives
Explanation
The business analysis information management approach governs how requirements and related information are structured, stored, accessed, and reused across the initiative. Strategic goals are set in strategy analysis, and solution testing belongs to solution evaluation. Task assignment is a project management function.
Question 5Business Analysis Planning and Monitoring
A business analyst is planning the level of detail appropriate for requirements documentation. Which factor most directly influences that decision?
- The intended use of the information and the needs of its audience Correct answer.
- The seniority of the project sponsor alone
- The number of past projects in the industry
- The color scheme of the organization's templates
Explanation
The appropriate level of detail depends on how the information will be used and who will consume it, such as developers needing precise specifications versus executives needing summaries. Templates, industry history, and sponsor seniority alone do not determine detail. The plan should match detail to purpose and audience.
Question 6Business Analysis Planning and Monitoring
Which technique is most useful during planning to estimate the effort needed for business analysis activities?
- Decision modeling
- Organizational modeling
- Estimation based on similar past initiatives Correct answer.
- Data flow diagramming
Explanation
Effort estimation for business analysis work is commonly supported by comparing to similar past initiatives and adjusting for differences. Decision modeling, data flow diagramming, and organizational modeling are analysis techniques rather than estimation methods. Estimation should be revisited as understanding improves.
Question 7Business Analysis Planning and Monitoring
Which statement best describes how business analysis planning and monitoring is performed across an initiative?
- It is performed only after the solution is delivered
- It is repeated and adjusted as the initiative progresses Correct answer.
- It is delegated entirely to the project sponsor
- It happens once at the start and is then closed permanently
Explanation
Planning and monitoring is iterative; the plan is revisited as new information emerges and progress is tracked against it. Treating it as a one-time event ignores the monitoring element. It is not deferred until delivery, and it is not solely the sponsor's responsibility.
Question 8Business Analysis Planning and Monitoring
A stakeholder with high influence and a negative attitude toward a change is identified during planning. What is the most appropriate planning response?
- Restrict the stakeholder's access to all project information
- Develop a targeted engagement approach to address concerns and build support Correct answer.
- Ignore the stakeholder because the attitude may change on its own
- Remove the stakeholder's concerns from the requirements backlog
Explanation
High influence combined with a negative attitude signals risk to the initiative, so the engagement approach should address concerns and seek support. Ignoring the stakeholder or suppressing concerns increases resistance. Restricting information from an influential stakeholder typically worsens opposition.
Question 9Business Analysis Planning and Monitoring
When planning business analysis activities, how should the business analyst treat dependencies on other teams such as legal or architecture review?
- Schedule all reviews at the very end of the initiative
- Identify them and sequence business analysis work to accommodate them Correct answer.
- Exclude them because they are outside business analysis scope
- Assume they will resolve themselves without scheduling
Explanation
Dependencies on other groups should be identified during planning and reflected in the sequencing of business analysis activities. Assuming self-resolution or deferring all reviews to the end creates avoidable delays. Even external reviews must be accounted for in the plan.
Question 10Business Analysis Planning and Monitoring
A business analyst is deciding how to track progress of business analysis work. Which approach best supports monitoring?
- Defining measurable completion criteria for business analysis deliverables Correct answer.
- Counting only the number of meetings held
- Waiting until the project closes to assess progress
- Relying on memory and informal conversations only
Explanation
Monitoring requires defined, measurable criteria so that progress and quality can be assessed objectively. Memory and informal conversation are unreliable, and post-close assessment is too late. Counting meetings measures activity, not the completion of business analysis work.
Question 11Business Analysis Planning and Monitoring
What distinguishes a business analysis governance approach from a stakeholder engagement approach?
- Governance addresses storage of requirements; engagement addresses traceability
- Governance addresses decision rights and approvals; engagement addresses collaboration and communication Correct answer.
- Governance addresses solution testing; engagement addresses strategy definition
- Governance addresses communication channels; engagement addresses approval authority
Explanation
Governance defines how decisions are made, who has authority, and how approvals occur. Engagement defines how the business analyst collaborates and communicates with stakeholders. Storage and traceability belong to information management, and testing and strategy are separate knowledge areas.
Question 12Business Analysis Planning and Monitoring
A project has a very short timeline and limited access to subject matter experts. What is the most appropriate planning adjustment?
- Abandon the plan and proceed without any structure
- Delay all business analysis work until experts become available
- Expand the scope to include every possible requirement
- Prioritize elicitation activities and use efficient techniques to focus on high-value requirements Correct answer.
Explanation
When time and access are constrained, the plan should prioritize activities and select efficient techniques so the most valuable requirements are captured. Expanding scope worsens the constraint, and abandoning planning removes control. Deferring all work risks missing the deadline entirely.
Question 13Business Analysis Planning and Monitoring
A business analyst needs to decide which requirements artifacts to produce. Which consideration is most relevant?
- The preferred color of the documentation template
- The project manager's personal writing style
- The methodology in use and the audience who will consume the artifacts Correct answer.
- The number of employees in the finance department
Explanation
Artifact selection should reflect the chosen methodology and the needs of the people who will use the information, such as models for technical audiences or narratives for business audiences. Template color and personal style are not substantive criteria, and department size is largely irrelevant.
Question 14Business Analysis Planning and Monitoring
Which situation best indicates that the business analysis plan should be revised?
- The team holds its regularly scheduled status meeting
- A stakeholder confirms an earlier assumption
- A new regulatory constraint is introduced that changes approval requirements Correct answer.
- A template is reformatted for readability
Explanation
A material change such as a new regulatory constraint affects governance and approvals, so the plan must be updated to reflect it. Routine meetings, confirmed assumptions, and cosmetic template changes do not by themselves require replanning. Monitoring exists to detect such triggers and respond.
Question 15Business Analysis Planning and Monitoring
How should a business analyst plan for the reuse of business analysis information across initiatives?
- Rely on individuals to remember prior requirements
- Discard all artifacts after each initiative to avoid clutter
- Define structure, access, and retention so information can be located and reused Correct answer.
- Store information only in personal email folders
Explanation
Reuse requires deliberate structure, access controls, and retention rules so that information can be found and trusted later. Discarding artifacts destroys value, and personal storage or memory is unreliable. The information management approach should make reuse practical.
Question 16Business Analysis Planning and Monitoring
A business analyst is estimating business analysis effort for a new initiative. Which practice improves the reliability of the estimate?
- Basing the estimate solely on the sponsor's opinion
- Using a single fixed number without review
- Avoiding any comparison to prior work
- Documenting assumptions and revising the estimate as understanding grows Correct answer.
Explanation
Estimates are more reliable when assumptions are documented and the estimate is refined as knowledge increases. A single unreviewed number or reliance on one opinion is fragile. Comparing with analogous prior work generally improves accuracy rather than harming it.
Question 17Business Analysis Planning and Monitoring
Which pair correctly matches a planning activity with its primary output?
- Elicitation with the governance approach
- Stakeholder analysis with the stakeholder engagement approach Correct answer.
- Traceability with the project budget
- Solution evaluation with the information management approach
Explanation
Stakeholder analysis directly informs the stakeholder engagement approach, which guides collaboration and communication. Traceability does not produce a budget, elicitation is separate from governance, and solution evaluation is not a source of the information management approach.
Question 18Business Analysis Planning and Monitoring
What is the primary role of the business analysis plan in relation to project management plans?
- It is unrelated to the project management plan
- It complements the project management plan by detailing business analysis work Correct answer.
- It must conflict with the project management plan
- It replaces the project management plan entirely
Explanation
The business analysis plan details the business analysis activities and should align with and complement the project management plan. It does not replace it, nor should the two be unrelated or in conflict. Alignment helps schedule and resource business analysis work realistically.
Question 19Business Analysis Planning and Monitoring
A business analyst discovers that a key stakeholder group was omitted from the initial engagement plan. What is the most appropriate action?
- Wait until the next initiative to include them
- Remove other stakeholders to keep the list size constant
- Update the engagement approach and communicate the change Correct answer.
- Proceed without them to avoid changing the plan
Explanation
Omitted stakeholders represent a planning gap, so the engagement approach should be updated and the change communicated to maintain transparency. Proceeding without them risks missing requirements and resistance. Deferring to a future initiative leaves the current work exposed, and removing others is arbitrary.
Question 20Business Analysis Planning and Monitoring
An organization uses a predictive methodology for one workstream and an adaptive methodology for another within the same initiative. How should the business analyst plan the work?
- Use the adaptive approach only for documentation and the predictive approach only for elicitation
- Apply a single rigid approach to both workstreams regardless of context
- Tailor the approach for each workstream while keeping governance coherent Correct answer.
- Refuse to plan until one methodology is chosen for the whole initiative
Explanation
Planning should be tailored to context, so different workstreams may warrant different levels of formality and cadence. Governance must still remain coherent so decisions and approvals are consistent. Forcing one rigid approach or refusing to plan ignores the reality of mixed environments.
Question 21Business Analysis Planning and Monitoring
Two business analysts on the same initiative apply different levels of detail to similar requirements. Which planning element would most directly prevent this inconsistency?
- A revised project budget
- A documented requirements structure and quality standards in the information management approach Correct answer.
- A new executive sponsor
- An additional status meeting
Explanation
Consistency in detail and quality is achieved by defining standards and structures for business analysis information in the information management approach. Budget changes, sponsor changes, and extra meetings do not establish requirements standards. Documented standards give analysts a shared reference.
Question 22Business Analysis Planning and Monitoring
A business analyst must decide how much upfront planning is warranted for a small, well-understood enhancement. What is the most defensible reasoning?
- Delegate planning decisions to the development team
- Skip planning entirely because the change is small
- Scale planning to the risk and complexity while retaining essential governance Correct answer.
- Apply the same planning effort as for a large complex program
Explanation
Planning effort should be proportional to risk and complexity, while essential governance such as approvals and traceability is retained. Applying full program-level planning to a small change is wasteful, and skipping planning removes control. Delegating planning to developers bypasses the business analyst's responsibility.
Question 23Business Analysis Planning and Monitoring
A business analyst is defining performance measures for monitoring business analysis work. Which set of measures best reflects meaningful monitoring?
- Total number of words written in all documents
- Number of coffee breaks and meeting room bookings
- Requirement approval cycle time and percentage of requirements traced to objectives Correct answer.
- Count of emails sent to stakeholders
Explanation
Meaningful measures reflect the quality and progress of business analysis work, such as approval cycle time and traceability to objectives. Activity counts like words, emails, or room bookings do not indicate whether the work is effective. Measures should support decisions, not just record activity.
Question 24Business Analysis Planning and Monitoring
A regulatory audit requires that every approved requirement be attributable to an authorizing decision. Which planning approach best satisfies this requirement?
- Store requirements without any linkage to decisions
- Apply the same approach used for unrelated marketing campaigns
- Define governance and traceability rules that link requirements to approvals and decision records Correct answer.
- Rely on verbal approvals recorded only in memory
Explanation
Auditability requires planned governance and traceability so each requirement can be linked to the decision that authorized it. Verbal approvals and unlinked storage cannot demonstrate attribution. Copying an unrelated approach ignores the specific regulatory requirement.
Question 25Elicitation and Collaboration
Which document is the primary output of the Plan Stakeholder Engagement process and guides how stakeholder communication and engagement will be carried out?
- Communications management plan
- Stakeholder register
- Stakeholder engagement plan Correct answer.
- Requirements traceability matrix
Explanation
The stakeholder engagement plan describes strategies and actions needed to promote productive stakeholder involvement across the project, including engagement levels and interrelationships. It is produced during planning and directs subsequent collaboration work. The communications management plan is a separate but related artifact focused on information flow.
Question 26Elicitation and Collaboration
During elicitation, a business analyst asks a group of subject matter experts to silently write ideas on sticky notes, post them, and then cluster related ideas before discussing. Which technique is being used?
- Brainstorming
- Focus groups
- Brain writing Correct answer.
- Interviews
Explanation
Brain writing is a variant of idea generation in which participants write ideas individually before sharing, which reduces groupthink and lets quieter members contribute. The silent writing and posting steps distinguish it from open verbal brainstorming. Clustering afterward supports organization of the collected ideas.
Question 27Elicitation and Collaboration
Which tool is most useful for visually capturing the flow of steps a customer takes when interacting with a service, including pain points?
- Decision tree
- Context diagram
- Customer journey map Correct answer.
- RACI matrix
Explanation
A customer journey map depicts the customer's end-to-end experience across touchpoints and highlights moments of friction or delight. It supports elicitation by revealing needs and improvement opportunities. Other tools serve different purposes, such as scope boundaries or decision logic.
Question 28Elicitation and Collaboration
What is the main purpose of the Confirm Elicitation Results activity?
- To schedule stakeholder meetings
- To verify that elicited information is accurate and consistent before it is used Correct answer.
- To document the solution design
- To estimate project costs
Explanation
Confirming elicitation results ensures that the information gathered is accurate, complete, and consistent with other information before it is relied upon. It compares elicitation outcomes against source information and resolves discrepancies. This step prevents flawed inputs from flowing into analysis and design.
Question 29Elicitation and Collaboration
Which of the following is an example of tacit knowledge that elicitation may need to surface?
- A completed requirements form
- A written procedure stored in a document repository
- An experienced employee's intuitive judgment about risk Correct answer.
- A published organizational policy
Explanation
Tacit knowledge is personal, experience-based, and hard to articulate, such as intuition or judgment built over years. Elicitation techniques like observation and interviews help surface it. Explicit knowledge, by contrast, is codified in documents and records.
Question 30Elicitation and Collaboration
A business analyst wants to observe how work is actually performed without interrupting employees. Which technique best fits this goal?
- Survey
- Workshop
- Document analysis
- Observation Correct answer.
Explanation
Observation lets the analyst watch work being performed in its real context, revealing actual practices that people may not describe accurately. Passive observation avoids disrupting the workers. It is especially useful for surfacing tacit knowledge and process detail.
Question 31Elicitation and Collaboration
Which elicitation technique is specifically designed to reach a large, geographically dispersed group of stakeholders efficiently?
- Focus group
- Prototyping
- Observation
- Survey or questionnaire Correct answer.
Explanation
Surveys and questionnaires can be distributed widely and completed asynchronously, making them efficient for large or dispersed audiences. They collect standardized responses at relatively low cost. Techniques like focus groups and observation require proximity and facilitation.
Question 32Elicitation and Collaboration
A stakeholder holds formal authority over the project budget and can approve or block funding. In a power/interest grid, where should this stakeholder be placed?
- High power, high interest Correct answer.
- High power, low interest
- Low power, low interest
- Low power, high interest
Explanation
Stakeholders with high power and high interest should be managed closely because they can significantly influence the project and care deeply about outcomes. Their authority to approve funding makes them critical to engage. Placement drives the engagement strategy in the stakeholder engagement plan.
Question 33Elicitation and Collaboration
During a facilitated workshop, two departments dispute a requirement's priority. What is the most appropriate action for the business analyst?
- Discard the requirement to avoid conflict
- Choose the priority of the department with the larger budget
- Record both positions and escalate the conflict to the sponsor for a decision Correct answer.
- End the workshop and reschedule it
Explanation
When stakeholders cannot reach consensus, the analyst documents the differing positions and escalates to an appropriate authority such as the sponsor. The analyst facilitates but does not unilaterally decide business priorities. Escalation preserves transparency and keeps the decision with those accountable.
Question 34Elicitation and Collaboration
A business analyst prepares a prototype for stakeholders to interact with and provide feedback on requirements. Which activity does this primarily support?
- Define the change strategy
- Elicit and confirm requirements through iterative feedback Correct answer.
- Perform solution evaluation
- Plan business analysis governance
Explanation
Prototyping supports elicitation by giving stakeholders something concrete to react to, which surfaces and refines requirements iteratively. Feedback cycles help confirm understanding. It is an elicitation and collaboration tool rather than a governance or evaluation activity.
Question 35Elicitation and Collaboration
Which technique is most appropriate for understanding the detailed steps and decision points in an existing process that stakeholders describe inconsistently?
- Survey
- Process modeling Correct answer.
- Mind mapping
- Brainstorming
Explanation
Process modeling creates a structured visual representation of activities, decision points, and flows, which helps reconcile inconsistent descriptions. It exposes gaps and disagreements that narrative accounts obscure. This makes it well suited to clarifying complex or disputed processes.
Question 36Elicitation and Collaboration
A business analyst needs to elicit requirements from executives who have very limited availability. Which approach is most effective?
- Hold a multi-day workshop with all executives
- Schedule brief, focused interviews with pre-circulated questions Correct answer.
- Send a long questionnaire and wait for responses
- Conduct open-ended observation of their daily work
Explanation
For time-constrained executives, short focused interviews with questions shared in advance respect their schedule while gathering high-value input. Pre-circulation improves efficiency and quality of responses. This balances thoroughness with limited availability.
Question 37Elicitation and Collaboration
What distinguishes a focus group from a workshop in the context of elicitation?
- A focus group produces a signed agreement, while a workshop produces only notes
- A focus group is conducted only with executives, while a workshop is only for end users
- A focus group always uses software, while a workshop never does
- A focus group gathers qualitative perceptions from selected participants, while a workshop brings stakeholders together to achieve a defined outcome Correct answer.
Explanation
A focus group is a facilitated discussion with pre-qualified participants used to gather qualitative impressions and perceptions. A workshop is a structured working session aimed at a specific deliverable, such as resolving requirements or reaching agreement. Their purposes and outputs differ accordingly.
Question 38Elicitation and Collaboration
A business analyst is preparing for elicitation and identifies that key stakeholders are unavailable during the planned window. What is the most appropriate response?
- Postpone elicitation indefinitely until everyone is available
- Proceed with available stakeholders and assume the missing input
- Adjust the elicitation approach and schedule to accommodate stakeholder availability Correct answer.
- Cancel the elicitation activity entirely
Explanation
Elicitation planning should adapt to stakeholder constraints, adjusting timing, techniques, or sequencing to obtain needed input. Flexibility preserves the value of stakeholder participation. Assuming or cancelling sacrifices information quality.
Question 39Elicitation and Collaboration
Which output of elicitation typically captures the raw, unconfirmed information gathered from stakeholders before it is analyzed and verified?
- Solution scope
- Elicitation results (unconfirmed) Correct answer.
- Approved requirements
- Business case
Explanation
Elicitation results are documented as unconfirmed until they are verified against other sources and stakeholders. This staging allows the analyst to organize and later confirm the information. Approved requirements and scope are downstream artifacts.
Question 40Elicitation and Collaboration
A stakeholder consistently provides vague answers during interviews. Which action best improves the quality of elicited information?
- Switch immediately to document analysis only
- Replace the stakeholder with someone else
- Ask open-ended questions and follow up with specific probing questions Correct answer.
- Record the vague answers as final requirements
Explanation
Combining open-ended questions with targeted probes encourages elaboration and clarifies vague responses. Probing helps uncover the detail needed for accurate requirements. This is a core interviewing skill for improving elicitation quality.
Question 41Elicitation and Collaboration
Which collaboration activity most directly ensures that stakeholders share a common understanding of agreed requirements?
- Sending requirements only to the project sponsor
- Distributing requirements for individual review with no discussion
- Facilitating a review session where stakeholders confirm and discuss requirements together Correct answer.
- Filing requirements without further communication
Explanation
A facilitated review where stakeholders discuss and confirm requirements together builds shared understanding and surfaces misunderstandings. Group confirmation reduces the risk of divergent interpretations. Passive distribution alone does not ensure common understanding.
Question 42Elicitation and Collaboration
A business analyst notices that a powerful stakeholder rarely attends engagement sessions but can veto decisions. Which engagement strategy is most appropriate?
- Keep informed and satisfied through targeted, proactive communication Correct answer.
- Engage only when problems arise
- Monitor with minimal effort
- Ignore the stakeholder since attendance is low
Explanation
Stakeholders with high power but low current interest should be kept satisfied through proactive, targeted communication so their concerns are addressed before they affect the project. Low attendance does not reduce their influence. Ignoring them risks late vetoes.
Question 43Elicitation and Collaboration
During a workshop, the business analyst uses a technique where participants vote on and rank a large list of candidate requirements to reach agreement. Which technique is this?
- Root cause analysis
- Document analysis
- Multivoting Correct answer.
- Interface analysis
Explanation
Multivoting is a group decision technique in which participants vote to narrow a large set of options down to the most favored ones. It helps groups prioritize and reach agreement efficiently. It is distinct from analysis techniques that examine documents, interfaces, or causes.
Question 44Elicitation and Collaboration
A business analyst is eliciting requirements for a replacement system and discovers that users rely on undocumented workarounds. Which combination of techniques best surfaces these workarounds?
- Document analysis alone
- Observation and interviews Correct answer.
- Decision modeling
- Surveys and questionnaires
Explanation
Undocumented workarounds are tacit practices unlikely to appear in documents or structured surveys. Observation reveals actual behavior, and interviews let users explain why they work around the system. Together they surface hidden practices effectively.
Question 45Elicitation and Collaboration
Two stakeholder groups provide conflicting definitions of a key business term used throughout the requirements. What is the most rigorous way to resolve this during elicitation and collaboration?
- Remove the term from all requirements
- Let each group keep its own definition silently
- Adopt the definition from the group with more seniority without discussion
- Create a glossary entry agreed by both groups and confirm it in a joint review Correct answer.
Explanation
Conflicting terminology is resolved by creating a shared glossary definition and confirming it with all affected stakeholders in a joint review. This ensures consistent interpretation across requirements. Silent divergence or unilateral adoption leaves ambiguity that propagates into the solution.
Question 46Elicitation and Collaboration
A business analyst must elicit requirements across several business units with competing priorities and limited time for joint sessions. Which approach best balances coverage and collaboration?
- Rely solely on document analysis of existing policies
- Skip elicitation and adopt the vendor's default requirements
- Use a combination of targeted individual sessions and a consolidated prioritization workshop Correct answer.
- Elicit only from the largest business unit and extrapolate to others
Explanation
Combining targeted individual sessions with a consolidated prioritization workshop gathers input from each unit while using a joint forum to reconcile competing priorities. This balances broad coverage with collaborative resolution. Extrapolating or skipping elicitation risks missing unit-specific needs.
Question 47Elicitation and Collaboration
After eliciting requirements, a business analyst finds that some confirmed requirements contradict earlier documented business rules. What is the most appropriate next step?
- Delete the business rules to eliminate the conflict
- Ignore the contradiction since the requirements were confirmed
- Investigate the source of the conflict and reconcile requirements with the business rules through stakeholder confirmation Correct answer.
- Escalate immediately without any analysis
Explanation
Contradictions between requirements and business rules signal a need to investigate and reconcile, confirming the correct position with stakeholders. Analysis before escalation ensures the issue is well understood. Deleting rules or ignoring conflicts risks an inconsistent solution.
Question 48Elicitation and Collaboration
A business analyst is deciding how much elicitation detail to plan for a low-risk, well-understood enhancement versus a high-uncertainty transformation. Which principle should guide the level of elicitation planning?
- Always maximize elicitation to be thorough
- Scale elicitation rigor and techniques to the uncertainty, complexity, and risk of the initiative Correct answer.
- Always minimize elicitation to save time
- Apply identical elicitation effort regardless of risk
Explanation
Elicitation planning should be proportionate to the initiative's uncertainty, complexity, and risk. High-uncertainty work needs more iterative and varied techniques, while well-understood low-risk work can use lighter approaches. Uniform effort misallocates resources in both directions.
Question 49Requirements Life Cycle Management
Which technique is used to assess how much a proposed change would affect a solution that is already in operation?
- Stakeholder mapping
- Prototyping
- Benchmarking
- Impact analysis Correct answer.
Explanation
Impact analysis evaluates the likely consequences of a change on solution components, stakeholders, and value delivery, and it is the standard technique for judging change effects during requirements life cycle management. It supports the assess step of the change process.
Question 50Requirements Life Cycle Management
What is the main purpose of tracing requirements?
- To assign work to team members
- To establish relationships that help show how requirements connect to each other and to other artifacts Correct answer.
- To convert requirements into test scripts
- To estimate the cost of building each requirement
Explanation
Tracing creates and maintains relationships between requirements and other artifacts such as goals, designs, and test cases. These relationships support coverage checks, impact analysis, and verification that requirements are met.