Midway through the requirements gathering phase, a stakeholder informs the business analyst that a requested requirement does not address the solution. The stakeholder wants to know who made the request. The business analyst spends hours searching emails to identify the requestor.

What should the business analyst have documented?

A. The source in the requirements traceability matrix

B. The source in the RACI matrix

C. Roles and responsibilities in the RACI matrix

D. Sponsor approval in the requirements traceability matrix

A business analyst captures an application's current limitations and consults with end users to identify new features for the next version. What can be used to analyze this information and determine project scope?

A. Root cause analysis

B. Capability table

C. As-is process

D. Requirements traceability matrix

Which statement accurately depicts what changes can be made to requirements after they are baselined?

A. Requirements can be changed through a defined process.

B. Requirements cannot be changed once development begins.

C. Requirements cannot be changed once user acceptance testing begins.

D. Requirements can be changed only with sponsor approval.

A business analyst has received a test result report that shows evidence of defective functionality. The business analyst checks the test result again and verifies that the functionality behaves according to the requirements.

At this point, the business analyst should first:

A. let the users decide if the test result is acceptable.

B. change the requirement according to the test result.

C. verify that the test case is incorrect.

D. ask the tester to perform the test again.

A business analyst has captured all of the requirements from the various stakeholders within the organization and has compiled them into a complete list. After reviewing the list of requirements with the stakeholders, it is determined that the list of requirements is too large and will exceed the allotted budget.

Which tool or technique should the business analyst use with the stakeholders to prioritize the requirements to determine which requirements are approved, deferred, or rejected?

A. SMART Goals

B. MoSCoW Analysis

C. SWOT Analysis

D. Timeboxing Analysis

A company is developing a new risk management system. The company expects the system to evolve in the near future due to changing government regulations.

Which approach will better cope with the requirements' volatility?

A. Multivoting

B. Phased baselining

C. Comparative analysis

D. Storyboarding

One of the main purposes for creating a requirements traceability matrix is to:

A. track how requirements can be connected to the solution.

B. provide test cases to validate solution deliverables.

C. document stakeholder approval of project requirements.

D. track the project solution scope.

A business analyst has elicited, documented, and verified the requirements, discovering that there are not enough resources to deliver all the requirements. Which technique should the business analyst employ to rectify the issue?

A. Hold a brainstorming workshop to build the rationale for the requirements.

B. Perform traceability to find out where the requirements originated.

C. Survey stakeholders on their likes and dislikes about the requirements.

D. Ask stakeholders to vote on the requirements.

A company has completed a major project within time, cost, and scope and satisfied high-level quality standards and marketing requests. However, the product was considered a complete failure by shareholders and the market due to low return on investment.

From the business analysis perspective, the main reason for this business failure was a failure to:

A. establish measurable success criteria in the business case.

B. gather the appropriate usability requirements.

C. set the product positioning.

D. review and evaluate market expectations.

After completing the requirements, the project manager and business analyst realize that the project scope is not feasible in the projected schedule. The business analyst needs to review the amount of work the team is capable of delivering based on the approved project schedule. Which prioritization technique should the business analyst use?

A. Multivoting

B. Time-boxing

C. Weighted ranking

D. SWOT analysis