PMI Updated PMI-PBA Exam Questions and Answers by humaira

The business case is a document that provides the justification for initiating a project or program. It describes the business problem or opportunity, the benefits and costs of the proposed solution, and the risks and assumptions involved. The business case also includes the intangible costs and benefits associated with the change, such as the disruption and short-term loss of productivity that the client anticipates. The business analyst can use the business case to communicate the value proposition of the project or program to the stakeholders and decision makers. References: PMI Guide to Business Analysis, Chapter 3, Section 3.2.1; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain II: Planning, Task 4.

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.

The requirements baseline is a set of approved and prioritized requirements that are used as the basis for the development scope. The requirements baseline defines what the project or program will deliver and what the stakeholders expect to receive. The requirements baseline also serves as a reference point for managing changes and measuring progress. References: PMI Guide to Business Analysis, Chapter 9, Section 9.3.1; PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, Domain IV: Traceability and Monitoring, Task 1.

 MoSCoW is a requirements prioritization method that classifies requirements into four categories: Must have, Should have, Could have, and Won’t have. This method helps the business analyst and the stakeholders to agree on the essential requirements that must be delivered within a fixed time frame, and the desirable requirements that can be deferred or dropped if necessary. MoSCoW is suitable for this project because it allows the business analyst to focus on the minimum viable product that meets the business need of replacing the current enrollment and billing software application before the vendor contract ends, and to cope with the large volume of requirements by prioritizing them based on their value and urgency. References: PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline1, page 18; Business Analysis for Practitioners: A Practice Guide2, page 92.