A business analyst is working on a project to update the user interface for a legacy procurement system. An end user raises concerns that the new solution will not support their core business processes.
How could the business analyst address the end user's concerns about the new interface?
Answer : B
According to the PMI Professional in Business Analysis objectives and content, a prototype is a tool that can be used to elicit, analyze, and validate requirements. A prototype is a representation of a solution that allows stakeholders to interact with it and provide feedback. By developing a prototype, the business analyst can gather functional requirements from the end user and ensure that the new interface supports their core business processes. A prototype can also help to reduce ambiguity, resolve conflicts, and increase stakeholder satisfaction.Reference:
PMI Professional in Business Analysis objectives and content:PMI-PBA Certification
PMI Professional in Business Analysis reference list:PBA Reference List
PMI Professional in Business Analysis study guide:PMI.com
In order to reduce product and project risk for a large, complex project, a business analyst is asked to help develop a change process that includes formal authorization and tracking throughout the life cycle of the project. The business analyst needs a capability that will help ensure that the product conforms to approved requirements, changes can be documented, and the status of each change can be
reported.
What should the business analyst use?
An organization is evaluating the possibility of conducting business internationally. Which factors should be investigated at the onset of the initiative?
How should a business analyst determine whether a solution satisfies business requirements?
Answer : B
According to the PMI Guide to Business Analysis, user acceptance testing is a technique that involves verifying and validating that the solution meets the business requirements and satisfies the stakeholder needs and expectations. User acceptance testing is usually performed by the end users or their representatives, who evaluate the solution against predefined acceptance criteria and provide feedback on its functionality, usability, performance, quality, etc. User acceptance testing can help to determine whether a solution satisfies business requirements, as it can demonstrate that the solution delivers the intended business value and benefits, and that it meets or exceeds the stakeholder satisfaction. By reviewing the results of user acceptance testing, a business analyst can assess how well the solution meets business requirements, and identify any gaps or issues that need to be addressed or resolved. Evaluating the solution against the project charter, conducting a brainstorming session with end users, or reviewing the traceability matrix are other ways to analyze and validate requirements, but they do not necessarily determine whether a solution satisfies business requirements, as they do not involve testing or evaluating the solution in real or simulated conditions.Reference: PMI Guide to Business Analysis, page 317-318.
A business analyst is assigned to a business process re-engineering project. In addition to planning a workshop to elicit requirements, the business analyst wants to send out a survey to gather data to use in a statistical analysis on user satisfaction with the current business process.
Which of the following types of surveys would be most appropriate to create and why?
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 company is developing a new product for a customer and is required to verify and validate the product against the customer's acceptance test plan and requirements. The product was successfully verified against the acceptance test criteria, but the customer
does not believe that the product meets the requirements.
This occurred because the customer's acceptance test plan:
Answer : D
Measurable and testable requirements are requirements that have clear and specific criteria that can be used to verify and validate the product against the customer's expectations. Measurable and testable requirements can help to avoid ambiguity, confusion, or disagreement between the customer and the company. If the customer's acceptance test plan did not have measurable and testable requirements, it could result in a situation where the product was successfully verified against the acceptance test criteria, but the customer did not believe that the product met the requirements.Reference: = PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline (2019), page 10; Business Analysis for Practitioners: A Practice Guide (2015), page 40.