Here you have the best PMI PMI-PBA practice exam questions
A business analyst is developing a traceability matrix to determine whether or not any gaps exist and to identify any discrepancies.
Which critical field is needed to ensure that the traceability matrix is usable?
A traceability matrix is designed to ensure that all requirements are accounted for throughout the project lifecycle, and no aspect is overlooked. The 'Requirements description' field is critical as it provides a comprehensive and clear description of what each requirement entails. This detailed information is essential for understanding the specific requirements or outcomes that need to be achieved, which is necessary to identify any gaps or discrepancies appropriately. Without a clear description of the requirements, it would be challenging to ensure traceability and verify that all business needs are met.
A business analyst has been asked to investigate a problem. This investigation will provide input towards developing a business case. The business analyst wants to first understand the company’s current business processes.
Which technique should the business analyst use?
To understand the company's current business processes, the business analyst should use Observation. Observation involves actively watching and documenting the company's activities and processes, allowing the analyst to see firsthand how work is conducted. This technique enables the identification of potential bottlenecks and inefficiencies within the current processes, providing valuable insights for developing a business case.
The customer and the business analyst are collaborating in the development of a solution scope. It is important for the customer to:
The customer is integral to the development of the solution scope and must invest the required time to provide, clarify, and elaborate on the requirements. This includes offering detailed descriptions and necessary constraints to ensure the solution aligns with their needs and expectations, and with overall business objectives.
A business analyst is leading a project to implement automated order entry software at a local pizza restaurant. The business analyst has very little information about the project: the ordering process takes too long and often ends in incorrect orders.
What step should the business analyst take next?
When leading a project to implement automated order entry software with little information available, the crucial initial step is to schedule requirements gathering sessions with key stakeholders, such as the manager of the ordering department. This will provide detailed insights into the current process issues, specific needs, and objectives. Understanding these aspects is essential to tailor the solution effectively and ensure the implemented software addresses the critical pain points. Identifying testing resources or selecting software without this foundational understanding would be premature.
After a project was delivered, the business analyst learns of a project objective with no associated requirement. What would have helped determine this issue before delivery?
Tracing requirements is the best way to ensure that every project objective has an associated requirement. This process involves linking each project objective to its corresponding requirements, verifying the completeness and coverage of all objectives throughout the development process. By doing this, any missing or unassociated requirements can be identified early, preventing issues from being discovered only after project delivery.