In the first few weeks after a large implementation of a new web-based application, a critical report failed. Further Investigation determined that a worker had been using a field that was not supposed to be used. This issue was not identified in testing. Which technique could have prevented this problem from occurring?
Correct Answer: C
Explanation According to the PMI Guide to Business Analysis, a use case is a technique that describes how an actor interacts with a system or a process to achieve a specific goal. A use case can help to prevent problems from occurring in the implementation of a new application, as it can capture the functional requirements and the expected behavior of the system or the process, as well as the exceptions and alternative flows. A use case can also help to design and execute test cases that cover all the possible scenarios and outcomes. In this case, a use case could have prevented the problem of a worker using a field that was not supposed to be used, as it could have specified the valid inputs and outputs for the report, and the actions and responses of the system or the process. Prototyping, diagrams, and document analysis are other techniques that can help to analyze and communicate requirements, but they do not necessarily prevent problems from occurring in the implementation of a new application, as they do not describe the interactions and outcomes of the system or the process in detail. References: PMI Guide to Business Analysis, page 165-166.
PMI-PBA Exam Question 2
The document that defines the process for managing requirements revisions is the:
Correct Answer: B
Explanation The change management plan outlines the process for managing changes to requirements, ensuring that any revisions are controlled and documented throughout the project lifecycle. References: PMI-PBA Examination Content Outline, Business Analysis for Practitioners: A Practice Guide.
PMI-PBA Exam Question 3
When modeling processes or analyzing tasks, business rules can be uncovered by asking about:
Correct Answer: C
Explanation Business rules are statements that define or constrain some aspect of the business, such as policies, standards, procedures, regulations, or constraints. Business rules can be uncovered by asking about the reasons for choosing a particular course of action when modeling processes or analyzing tasks. By asking why a certain decision is made, what criteria are used, what conditions are applied, or what consequences are expected, the business analyst can elicit the business rules that govern the behavior or outcome of the process or task. Asking about tasks that overlap with each other, work that may be performed out of sequence, or task transitions that hinder organizational performance may help to identify issues or opportunities for improvement in the process or task, but they may not reveal the business rules that underlie them. References: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 15; Business Analysis for Practitioners: A Practice Guide2, page 95.
PMI-PBA Exam Question 4
A business analyst is working with the project manager, company auditors, and project stakeholders to determine whether formal signoff should be required for the project. For which reason would the business analyst recommend formal signoff to the group?
Correct Answer: C
Explanation The business analyst would recommend formal signoff to the group if errors in the product could result in financial solvency. Formal signoff is a process that ensures that the stakeholders agree on and approve the requirements and deliverables of the project. Formal signoff can help to reduce ambiguity, confusion, or disputes among the stakeholders and increase their accountability and commitment to the project. Formal signoff is especially important when errors in the product could result in financial solvency, as it implies that there is a high level of risk, complexity, or regulation involved in the project and that any mistake or defect could have severe consequences for the organization or its customers. The industry being unregulated is not a reason to recommend formal signoff to the group, as it implies that there is less need for compliance or verification of the product quality or performance. The project impact being contained within a small department of the company is not a reason to recommend formal signoff to the group, as it implies that there is less stakeholder involvement or interest in the project outcome or value. The organization following an iterative project life cycle is not a reason to recommend formal signoff to the group, as it implies that there is more flexibility and adaptability in the project scope and deliverables and that feedback and validation are obtained frequently throughout the project. References: Business Analysis for Practitioners: A Practice Guide 1, page 113-114; PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline 2, page 17.
PMI-PBA Exam Question 5
The project team has all the document control process and versioning in place to capture the requirements changes. The team ensures that the change is documented in the scope document, resulting in the changed work breakdown schedule (WBS) and schedule. However, a key requirement was not implemented in the release. Which is a possible reason why the requirement was not implemented?
Correct Answer: C
Explanation A requirements traceability matrix is a tool that links the requirements to their sources, objectives, and deliverables. It helps to track the status, changes, and verification of each requirement throughout the project life cycle. If the requirements traceability matrix was not updated with the change, it could result in a key requirement being missed or overlooked in the implementation. The other options are not likely to cause this problem. The requirements management plan is a document that describes how the requirements will be elicited, analyzed, documented, validated, and managed. The scope management plan is a document that describes how the project scope will be defined, controlled, and verified. The schedule management plan is a document that describes how the project schedule will be developed, monitored, and controlled. References: PMI-PBA Examination Content Outline, page 13; PMI-PBA Reference List, page 1, BABOK Guide v3, page 39; 6.
