PMI Updated PMI-PBA Exam Questions and Answers by archibald

 A traceability matrix is a document that the business analyst can use to determine the relationship of each requirement to the business need when working on Project Y. A traceability matrix is a table that shows how each requirement relates to other project artifacts, such as business needs, objectives, deliverables, design elements, test cases, or risks. A traceability matrix can help to ensure that each requirement is aligned with and contributes to the business need that initiated the project. It can also help to verify that each requirement is necessary, feasible, testable, and traceable throughout the project life cycle. A traceability matrix can also help to manage changes and measure progress in relation to the business need. A requirements baseline document is a version of the requirements specification that has been reviewed, approved, and formally established as the basis for further development and delivery of the solution. A requirements baseline document defines the scope of the project and the expected value of the solution. It does not show how each requirement relates to the business need explicitly. A requirements management plan is a document that describes how requirements will be elicited, analyzed, documented, validated, and managed throughout the project. A requirements management plan defines the roles, responsibilities, processes, and tools for managing requirements. It does not indicate the relationship of each requirement to the business need specifically. A requirements package is a document that presents the requirements in a structured and organized way for communication and verification purposes. A requirements package may include different types of requirements, such as functional, non-functional, quality, or transition requirements. It does not demonstrate how each requirement relates to the business need directly. A reliability matrix is not a standard document in business analysis, but it may refer to a tool that measures the reliability or dependability of a system or a process. A reliability matrix evaluates the performance or quality of a solution. It does not determine the relationship of each requirement to the business need. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.

The business analyst is using a bottom-up estimation technique, which involves breaking down the work into smaller components and estimating the time and resources needed for each component. Then, the estimates are aggregated to obtain the total estimate for the project. Bottom-up estimation is more accurate and reliable than other techniques, but it also requires more time and effort. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 85.

 Acceptance criteria are the conditions that must be met for a solution or deliverable to be accepted by the stakeholders. Acceptance criteria should be measurable, testable, and clear, so that the team can verify if the requirements have been met or not. If the acceptance criteria for the requirements were not measurable, the team would have difficulty confirming if certain requirements have been met, as they would not have a clear and objective way to evaluate the solution or deliverable. The other options are not likely to cause this issue. The test engineer is not responsible for communicating requirements to the team, but for testing them against the acceptance criteria. Not all stakeholders need to be involved during requirements elicitation, as long as the key stakeholders who can provide relevant and accurate information are consulted. Requirements should be adequately reviewed with the project sponsor, but this does not affect the confirmation of meeting the requirements, as the sponsor is not the one who verifies them. References: PMI-PBA® Examination Content Outline, page 13; PMI-PBA® Reference List, page 1, BABOK® Guide v3, page 39.

Requirements baseline is the approved version of the requirements document that serves as a reference point for further changes. Requirements can be changed after they are baselined through a defined process that involves submitting a change request, analyzing the impact of the change, obtaining approval from the stakeholders, updating the requirements document, and communicating the change to the project team and other affected parties. Requirements can be changed at any stage of the project life cycle as long as they follow the defined process. References: = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 10; Business Analysis for Practitioners: A Practice Guide (2015), page 40.