The PMI Professional in Business Analysis (PMI-PBA)

 Time-boxing is a prioritization technique that involves assigning a fixed amount of time or resource to each requirement or deliverable, and delivering as much value as possib le within that time or resource constraint. Time-boxing is useful when the project has a tight timeline or budget, and the stakeholders have too many requirements for the delivery window.  Time-boxing helps to focus on the most important and valuabl e requirements, and to manage the expectations and scope of th e stakeholders.  References : PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 1 , page 18; Business Analysis for Practitioners: A Practice Guide 2 , page 97.

Nonfunctional requirements are the characteristics or qualities of a solution that describe how well it performs or operates. They include aspects such as usability, reliability, availability, scalability, security, p erformance, etc. The website crashing frequently indicates that the nonfunctional requirements related to availability and performance were not identified and tested properly. Quality attributes are another term for nonfunctional requirements, so option A is equivalent to option C. Critical business requirements and essential product requirements are both functional requirements, which describe what a solution does or provides, not how well it does it. Therefore, options B and D are incorrect.  References : P MI Professional in Business Analysis (PMI-PBA)® Examination Content Outline, page 18; Business Analysis for Practitioners: A Practice Guide, page 114-115.

Internal rate of return (IRR) is a technique that calculates the annualized rate of return of an investment or a project. IRR can help the business anal yst to determine the estimated growth rate of potential solution options by comparing the present value of the expected cash inflows and outflows of each option. IRR can also help to select the option that has the highest rate of return and exceeds the min imum required rate of return or the cost of capital.  References : = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 11; Business Analysis for Practitioners: A Practice Guide (2015), page 66.

Observation is a technique that involves watching how people perform their work in their natural environment. Observation can help the business analyst to understand the company’s current business processes, identify pain points, and discover opportunities for improvement. Observation can also help to validate or verify the information obtained from other sources, such as interviews or documents.  References : = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 9; Business Analysis for Practitioners: A Practice Guide (2015), page 61.

The best course of action to take when the customer reports defects after implementation of the product is to compare reported defects with user accepta nce test results. User acceptance testing (UAT) is a process of verifying that the solution meets the requirements and expectations of the end users and delivers value to them. User acceptance testing involves preparing test cases, scenarios, or scripts ba sed on the acceptance criteria, executing them with representative users or stakeholders, collecting feedback, identifying defects or issues, and obtaining sign-off or approval for deployment. By comparing reported defects with user acceptance test results , the business analyst can determine whether the defects were already detected and resolved during UAT, whether they were missed or overlooked during UAT, or whether they emerged after UAT due to changes in the environment, configuration, data, or usage. T his can help to assess the impact and severity of the defects and decide on the appropriate actions to address them. Escalating the issue to the project manager since the acceptance was given by the customer is not helpful, as it does not involve investiga ting or resolving the defects. Doing nothing since the solution is now the responsibility of the operations manager is not responsible, as it does not ensure customer satisfaction or solution quality.  Involving the end users and planning a new rou nd of acceptance tests to check the gaps is not feasible, as it may be costly, time-consuming, and disruptive to cond uct another UAT after implementation.  References : PMI Professional in Business Analysis (PMI-PBA)® Examinati on Content Outline 1 , page 14; Business Analysis for Practitioners: A Practice Guide 2 , page 80.

Status is a critical field that is needed to ensure that the traceability matrix is usable. Status indicates the current st ate of each requirement, such as approved, deferred, implemented, tested, or verified. Status helps to track the progress and completion of requirements throughout the project life cycle. It also helps to identify any gaps or discrepancies that may exist b etween the requirements and the project deliverables.  References : = PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline (2019), page 10; Business Analysis for Practitioners: A Practice Guide (2015), page 40.

 A change control proc ess is a set of procedures that defines how changes to the requirements are identified, assessed, approved, implemented, and communicated. A change control process helps to ensure that changes are aligned with the business objectives, do not introduce unne cessary risks, and do not adversely affect the quality of the solution.  A change control process also helps to manage stakeholder expectations and avoid scope creep.  References : PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 1 , page 13; Business Analysis for Practitioners: A Practice Guide 2 , page 77.

A requirements traceability matrix is a tool that links the requirements to their sources, objectives, and deliverab les. 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 do cument 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 .

The purpose of reviewing the system use cases and screen mockups with the client team is to validate that the system is aligned with the stakeholder requirements. Validation is a process of ensuring that the solution meets the needs and expectations of the stakeholders and delivers value to them. Validation involves checking whether the solution is feasible, acceptable, complete, corre ct, consistent, and testable. By walking through the artifacts with the client team, the business analyst can obtain feedback, confirm understanding, identify gaps or errors, and resolve issues. Verifying that the documents are aligned with the transition requirements or the solution requirements are possible outcomes of the review meeting, but they are not the main purpose.  V erifying that the system is aligned with the quality requirements is not relevant to this scenario, as quality requirements are related to how well the solution performs rather than wh at it does.  References : PMI Professional in Business Analysis (PMI-PBA)® Examination Content Outline 1 , page 13; Business Analysis for Practitioners: A Practice Guide 2 , page 76.