A business analyst (BA) will regularly perform stakeholder analysis to understand which of the following?
Answer : A
Stakeholder analysis is a technique used by business analysts to understand the attitudes and influence of various stakeholders. This involves identifying stakeholders, assessing their interests, influence, and the impact they can have on the project. Understanding stakeholders' attitudes and influence helps in managing their expectations, securing their support, and mitigating potential risks associated with stakeholder engagement.
: The BABOK Guide discusses stakeholder analysis as a part of the underlying competencies that a business analyst should develop.It is crucial for the success of any initiative to identify stakeholders, analyze their influence and impact levels, and maintain communication with them even when situations or people change1.Additionally, stakeholder relationship management is listed as one of the core business analyst skills in the BABOK Guide2.
(Which of the following BEST describes how value is created within an organization through business analysis?)
Answer : D
The correct answer is D. IIBA's Business Analysis Standard explains that business analysis creates value throughout the organization, across strategic, tactical, and operational levels, and over various timeframes. It also emphasizes continuously assessing and prioritizing work to maximize the value being delivered. Because option D includes both continuous evaluation and alignment with immediate and long-term goals, it is the best match to the IIBA view of value creation.
Option A is incorrect because it focuses too narrowly on short-term needs and compliance. IIBA's framework is broader and includes long-term strategic outcomes in addition to tactical and operational value.
Option B is incomplete. Stakeholder feedback is important in business analysis, but value is not created only by responding to stakeholder preferences. IIBA ties value creation to achieving desired outcomes, making sound decisions, and aligning work across multiple organizational horizons.
Option C is not the best answer because it is too narrow and software-focused. Business analysis is not limited to software delivery, and IIBA defines it much more broadly as enabling change and delivering value across the organization.
Which requirements are temporary in nature?
Answer : D
Transition requirements are the only category of requirements that are temporary in nature. They define the capabilities that a solution must have to facilitate the transition from the current state to the future state, but they are not needed once the transition is complete. These include data conversion, training, and deployment needs.
They support the implementation but are not part of the long-term functioning solution. This distinguishes them from business, stakeholder, and solution requirements, which are ongoing or permanent once implemented.
BABOK Guide v3 -- Section 2.3.4: Transition Requirements:
''Transition requirements describe the capabilities that the solution must have to facilitate transition from the current state to the future state, but that will not be needed once that transition is complete.''
What is used for quality control when verifying requirements and designs?
Answer : B
A checklist is a quality control tool used to ensure that requirements and designs meet specific criteria before they are finalized. It helps analysts systematically verify completeness, correctness, clarity, feasibility, and testability of requirements or design elements. Checklists serve as a structured way to reduce omissions and improve quality during the verification process.
Used during:
Requirements validation
Design reviews
Peer and stakeholder reviews
BABOK Reference:
Located in the Requirements and Design Definition knowledge area, specifically under ''Verify Requirements,'' where checklists are mentioned as a technique for ensuring quality and completeness.
When undertaking requirements verification, who determines if the requirements captured are of good quality?
Answer : A
When undertaking requirements verification, the stakeholders who will be using the requirements are best positioned to determine if they are of good quality. These stakeholders have the practical experience and understanding of their needs and the context in which the requirements will be used. Their feedback ensures that the requirements are relevant, complete, and feasible. Involving stakeholders in the verification process helps in aligning the requirements with actual business needs and ensures that the final solution will be effective and satisfactory.
*Business Analysis.pdf, Section on 'Requirements Validation,' which discusses the role of stakeholders in verifying and validating requirements.
Why consider both tangible and intangible costs and benefits when determining the value of a solution?
Answer : D
Considering both tangible and intangible costs and benefits provides a complete estimate of the solution's value to the business. Tangible elements are directly measurable (e.g., cost savings, revenue), while intangible benefits (e.g., customer satisfaction, brand reputation) contribute to the strategic vision and long-term value.
Exact Extract from BABOK Guide v3 -- Section 7.6: Analyze Potential Value and Recommend Solution:
''Consideration should be given to both tangible and intangible value, including potential benefits and costs, to understand the overall impact of a proposed solution.''
(Your team's morale is low after recently launching a product that was misaligned with organizational strategy. In tracing requirements and designs for a new product, which technique would reduce the risk of another misalignment MOST effectively?)
Answer : B
The correct answer is B. BABOK's Trace Requirements task and related task card identify Scope Modelling as a technique used to visually depict scope and trace requirements to the area of scope the requirement supports. Since the problem in the scenario is misalignment, using scope modelling helps ensure requirements and designs are connected to the correct scope areas and remain aligned with what the initiative is intended to achieve.
Option A is incorrect because prototyping can help stakeholders visualize a solution, but it does not itself provide the strongest tracing mechanism for maintaining alignment between requirements, designs, and scope.
Option C is incorrect because SWOT analysis is used to assess strengths, weaknesses, opportunities, and threats. It is not a tracing technique, and the phrasing about duplicating a competitor's threat is not BABOK-aligned.
Option D is incorrect because observation can help understand user work or behavior, but it is not the best technique for tracing requirements and designs to avoid strategic or scope misalignment.